From autoconf-bounces@ietf.org Thu Oct 04 17:15:45 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IdY2b-0005Yh-Vz; Thu, 04 Oct 2007 17:15:29 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1IdY2a-0005WZ-RU for autoconf-confirm+ok@megatron.ietf.org; Thu, 04 Oct 2007 17:15:28 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IdY2a-0005W5-8d; Thu, 04 Oct 2007 17:15:28 -0400 Received: from ns1.neustar.com ([156.154.16.138]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IdY2Z-0000zb-3l; Thu, 04 Oct 2007 17:15:28 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 2F4B526EAA; Thu, 4 Oct 2007 21:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IdY2A-0006E9-2c; Thu, 04 Oct 2007 17:15:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Thu, 04 Oct 2007 17:15:02 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Cc: autoconf@ietf.org Subject: [Autoconf] I-D ACTION:draft-ietf-autoconf-manetarch-06.txt X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: autoconf-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Ad-Hoc Network Autoconfiguration Working Group of the IETF. Title : Mobile Ad hoc Network Architecture Author(s) : I. Chakeres, et al. Filename : draft-ietf-autoconf-manetarch-06.txt Pages : 20 Date : 2007-10-4 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. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-autoconf-manetarch-06.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-autoconf-manetarch-06.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-autoconf-manetarch-06.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-10-4163725.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-autoconf-manetarch-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-autoconf-manetarch-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-10-4163725.I-D@ietf.org> --OtherAccess-- --NextPart 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://www1.ietf.org/mailman/listinfo/autoconf --NextPart-- From autoconf-bounces@ietf.org Mon Oct 08 04:00:37 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IenX9-0002DX-PL; Mon, 08 Oct 2007 04:00:11 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1IenX8-0002A4-HO for autoconf-confirm+ok@megatron.ietf.org; Mon, 08 Oct 2007 04:00:10 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IenX8-00026x-7g for autoconf@ietf.org; Mon, 08 Oct 2007 04:00:10 -0400 Received: from outbound.mailhop.org ([63.208.196.171]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IenWx-00069N-2l for autoconf@ietf.org; Mon, 08 Oct 2007 04:00:05 -0400 Received: from aste-genev-bois-153-1-42-173.w83-200.abo.wanadoo.fr ([83.200.92.173] helo=[192.168.147.106]) by outbound.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1IenWc-0003MQ-Db for autoconf@ietf.org; Mon, 08 Oct 2007 03:59:38 -0400 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 83.200.92.173 X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+VQnBuBjgMxN/VEfAJaMrE Mime-Version: 1.0 (Apple Message framework v752.3) References: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <5F17CFEE-B601-4990-AB62-67E895BFC55C@polytechnique.fr> Content-Transfer-Encoding: 7bit From: Thomas Clausen Date: Mon, 8 Oct 2007 09:59:35 +0200 To: autoconf@ietf.org X-Mailer: Apple Mail (2.752.3) X-Spam-Score: 0.0 (/) X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b Subject: [Autoconf] Regarding draft-ietf-autoconf-manetarch-06.txt X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: autoconf-bounces@ietf.org All, As you'll have noted, there have been some comments on the I-D draft- ietf-autoconf-manetarch as it was undergoing WGLC. Many thanks to those that have reviewed the document and provided their valuable feedback -- which has been integrated as best possible into this -06 version. I'd like to ask y'all, and specifically those who were providing feedback during WGLC, to quickly review this -06, specifically to understand if we can progress the document, or if there are still issues that we need to address. I'll note that the WGLC ended on September 24, and that this -06 should include all comments received during the WGLC. If you could let your opinion be known on the 'list within this week, then it'd be very helpful. Thanks Thomas Begin forwarded message: > From: Internet-Drafts@ietf.org > Date: 4October , 2007 11:15:02 PM CEDT > To: i-d-announce@ietf.org > Cc: autoconf@ietf.org > Subject: I-D ACTION:draft-ietf-autoconf-manetarch-06.txt > Reply-To: internet-drafts@ietf.org > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Ad-Hoc Network Autoconfiguration > Working Group of the IETF. > > Title : Mobile Ad hoc Network Architecture > Author(s) : I. Chakeres, et al. > Filename : draft-ietf-autoconf-manetarch-06.txt > Pages : 20 > Date : 2007-10-4 > > 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. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-autoconf- > manetarch-06.txt > > To remove yourself from the I-D Announcement list, send a message to > i-d-announce-request@ietf.org with the word unsubscribe in the body of > the message. > You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce > to change your subscription settings. > > Internet-Drafts are also available by anonymous FTP. Login with the > username "anonymous" and a password of your e-mail address. After > logging in, type "cd internet-drafts" and then > "get draft-ietf-autoconf-manetarch-06.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-autoconf-manetarch-06.txt". > > NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > Content-Type: text/plain > Content-ID: <2007-10-4163725.I-D@ietf.org> > > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/i-d-announce -- Thomas Clausen Thomas@thomasclausen.org http://www.thomasclausen.org/ http://hipercom.thomasclausen.org/ _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www1.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Mon Oct 08 11:17:14 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IeuLq-0006rs-ET; Mon, 08 Oct 2007 11:16:58 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1IeuLo-0006qg-Q3 for autoconf-confirm+ok@megatron.ietf.org; Mon, 08 Oct 2007 11:16:56 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IeuLo-0006qX-Di for autoconf@ietf.org; Mon, 08 Oct 2007 11:16:56 -0400 Received: from slb-smtpout-01.boeing.com ([130.76.64.48]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IeuLn-0003ZN-L9 for autoconf@ietf.org; Mon, 08 Oct 2007 11:16:56 -0400 Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id l98FGrCE001309 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 8 Oct 2007 08:16:54 -0700 (PDT) Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id l98FGr6I011931; Mon, 8 Oct 2007 10:16:53 -0500 (CDT) Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id l98FGewH011576; Mon, 8 Oct 2007 10:16:51 -0500 (CDT) Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 8 Oct 2007 08:16:47 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Autoconf] Regarding draft-ietf-autoconf-manetarch-06.txt Date: Mon, 8 Oct 2007 08:16:47 -0700 Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029EDB1C@XCH-NW-7V2.nw.nos.boeing.com> In-Reply-To: <5F17CFEE-B601-4990-AB62-67E895BFC55C@polytechnique.fr> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Autoconf] Regarding draft-ietf-autoconf-manetarch-06.txt Thread-Index: AcgJgis+sfBB9h3jS12wvGiHRcLg9gAOdMgw References: <5F17CFEE-B601-4990-AB62-67E895BFC55C@polytechnique.fr> From: "Templin, Fred L" To: "Thomas Clausen" , X-OriginalArrivalTime: 08 Oct 2007 15:16:47.0823 (UTC) FILETIME=[3E91ADF0:01C809BE] X-Spam-Score: 0.0 (/) X-Scan-Signature: 789c141a303c09204b537a4078e2a63f Cc: X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: autoconf-bounces@ietf.org Thomas, > I'd like to ask y'all, and specifically those who were providing =20 > feedback during WGLC, to quickly review this -06, I guess that includes me, and I will do my best to respond asap but have a busy week ahead of me. But, one comment for now wrt to the "acknowledgements" section: "While not entirely complete the authors would like to in particular thank the following individuals for exhaustive discussions and valuable contributions:" ^^^^^^^^^^ I don't quite understand the characterization of "exhaustive"? This document has been moved through the process more quickly than most (which often undergo intensive scrutiny over the course of many years) and I don't see any of them complaining. (There wasn't even an issue tracker maintained for this one.) Meanwhile, development of the MANET architecture has evloved over the course of several decades and I won't even guess as to how many vital contributers involved and R&D $'s invested. It would be good if this could be re-worded. Fred fred.l.templin@boeing.com =20 =20 > -----Original Message----- > From: Thomas Clausen [mailto:Thomas.Clausen@polytechnique.fr]=20 > Sent: Monday, October 08, 2007 1:00 AM > To: autoconf@ietf.org > Subject: [Autoconf] Regarding draft-ietf-autoconf-manetarch-06.txt=20 >=20 > All, >=20 > As you'll have noted, there have been some comments on the I-D draft-=20 > ietf-autoconf-manetarch as it was undergoing WGLC. Many thanks to =20 > those that have reviewed the document and provided their valuable =20 > feedback -- which has been integrated as best possible into this -06 =20 > version. >=20 > I'd like to ask y'all, and specifically those who were providing =20 > feedback during WGLC, to quickly review this -06, specifically to =20 > understand if we can progress the document, or if there are still =20 > issues that we need to address. I'll note that the WGLC ended on =20 > September 24, and that this -06 should include all comments received =20 > during the WGLC. >=20 > If you could let your opinion be known on the 'list within=20 > this week, =20 > then it'd be very helpful. >=20 > Thanks >=20 > Thomas >=20 > Begin forwarded message: >=20 > > From: Internet-Drafts@ietf.org > > Date: 4October , 2007 11:15:02 PM CEDT > > To: i-d-announce@ietf.org > > Cc: autoconf@ietf.org > > Subject: I-D ACTION:draft-ietf-autoconf-manetarch-06.txt > > Reply-To: internet-drafts@ietf.org > > > > A New Internet-Draft is available from the on-line Internet-Drafts > > directories. > > This draft is a work item of the Ad-Hoc Network Autoconfiguration =20 > > Working Group of the IETF. > > > > Title : Mobile Ad hoc Network Architecture > > Author(s) : I. Chakeres, et al. > > Filename : draft-ietf-autoconf-manetarch-06.txt > > Pages : 20 > > Date : 2007-10-4 > > =09 > > This document discusses Mobile Ad hoc NETworks (MANETs). =20 > It presents > > the initial motivation for MANET and describes unaccustomed > > characteristics and challenges. It also defines a MANET, other =20 > > MANET > > entities, and MANET architectural concepts. > > > > A URL for this Internet-Draft is: > > http://www.ietf.org/internet-drafts/draft-ietf-autoconf-=20 > > manetarch-06.txt > > > > To remove yourself from the I-D Announcement list, send a message to > > i-d-announce-request@ietf.org with the word unsubscribe in=20 > the body of > > the message. > > You can also visit=20 > https://www1.ietf.org/mailman/listinfo/I-D-announce > > to change your subscription settings. > > > > Internet-Drafts are also available by anonymous FTP. Login with the > > username "anonymous" and a password of your e-mail address. After > > logging in, type "cd internet-drafts" and then > > "get draft-ietf-autoconf-manetarch-06.txt". > > > > A list of Internet-Drafts directories can be found in > > http://www.ietf.org/shadow.html > > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > > Internet-Drafts can also be obtained by e-mail. > > > > Send a message to: > > mailserv@ietf.org. > > In the body type: > > "FILE /internet-drafts/draft-ietf-autoconf-manetarch-06.txt". > > =09 > > NOTE: The mail server at ietf.org can return the document in > > MIME-encoded form by using the "mpack" utility. To use this > > feature, insert the command "ENCODING mime" before the "FILE" > > command. To decode the response(s), you will need "munpack" or > > a MIME-compliant mail reader. Different MIME-compliant=20 > mail readers > > exhibit different behavior, especially when dealing with > > "multipart" MIME messages (i.e. documents which have been split > > up into multiple messages), so check your local documentation on > > how to manipulate these messages. > > > > Below is the data which will enable a MIME compliant mail reader > > implementation to automatically retrieve the ASCII version of the > > Internet-Draft. > > Content-Type: text/plain > > Content-ID: <2007-10-4163725.I-D@ietf.org> > > > > _______________________________________________ > > I-D-Announce mailing list > > I-D-Announce@ietf.org > > https://www1.ietf.org/mailman/listinfo/i-d-announce >=20 > --=20 > Thomas Clausen > Thomas@thomasclausen.org > http://www.thomasclausen.org/ > http://hipercom.thomasclausen.org/ >=20 >=20 >=20 >=20 > _______________________________________________ > Autoconf mailing list > Autoconf@ietf.org > https://www1.ietf.org/mailman/listinfo/autoconf >=20 _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www1.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Mon Oct 08 18:35:36 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1If1CA-0001UL-W4; Mon, 08 Oct 2007 18:35:27 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1If1C9-0001S1-3r for autoconf-confirm+ok@megatron.ietf.org; Mon, 08 Oct 2007 18:35:25 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1If1C8-0001Rt-Q4 for autoconf@ietf.org; Mon, 08 Oct 2007 18:35:24 -0400 Received: from outbound.mailhop.org ([63.208.196.171]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1If1C2-0006xG-KN for autoconf@ietf.org; Mon, 08 Oct 2007 18:35:24 -0400 Received: from aste-genev-bois-153-1-52-8.w81-249.abo.wanadoo.fr ([81.249.146.8] helo=[192.168.147.106]) by outbound.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1If1Bs-000LjV-3b; Mon, 08 Oct 2007 18:35:08 -0400 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 81.249.146.8 X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/IcuOBiGnZlrIIKDEOSArT In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1029EDB1C@XCH-NW-7V2.nw.nos.boeing.com> References: <5F17CFEE-B601-4990-AB62-67E895BFC55C@polytechnique.fr> <39C363776A4E8C4A94691D2BD9D1C9A1029EDB1C@XCH-NW-7V2.nw.nos.boeing.com> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <6428385A-F072-4AA0-A6B9-631496A1F4E6@polytechnique.fr> Content-Transfer-Encoding: 7bit From: Thomas Clausen Subject: Re: [Autoconf] Regarding draft-ietf-autoconf-manetarch-06.txt Date: Tue, 9 Oct 2007 00:35:05 +0200 To: "Templin, Fred L" X-Mailer: Apple Mail (2.752.3) X-Spam-Score: 0.0 (/) X-Scan-Signature: d890c9ddd0b0a61e8c597ad30c1c2176 Cc: autoconf@ietf.org X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: autoconf-bounces@ietf.org Fred, Thanks -- if you have a proposed preferred phrase to replace the one indicated, then I'm all ears ;) Cheers, Thomas On 8Oct , 2007, at 5:16 PM, Templin, Fred L wrote: > Thomas, > >> I'd like to ask y'all, and specifically those who were providing >> feedback during WGLC, to quickly review this -06, > > I guess that includes me, and I will do my best to respond > asap but have a busy week ahead of me. But, one comment for > now wrt to the "acknowledgements" section: > > "While not entirely complete the authors would like to in > particular > thank the following individuals for exhaustive discussions and > valuable contributions:" ^^^^^^^^^^ > > I don't quite understand the characterization of "exhaustive"? > This document has been moved through the process more quickly > than most (which often undergo intensive scrutiny over the > course of many years) and I don't see any of them complaining. > (There wasn't even an issue tracker maintained for this one.) > Meanwhile, development of the MANET architecture has evloved > over the course of several decades and I won't even guess as > to how many vital contributers involved and R&D $'s invested. > > It would be good if this could be re-worded. > > Fred > fred.l.templin@boeing.com > > >> -----Original Message----- >> From: Thomas Clausen [mailto:Thomas.Clausen@polytechnique.fr] >> Sent: Monday, October 08, 2007 1:00 AM >> To: autoconf@ietf.org >> Subject: [Autoconf] Regarding draft-ietf-autoconf-manetarch-06.txt >> >> All, >> >> As you'll have noted, there have been some comments on the I-D draft- >> ietf-autoconf-manetarch as it was undergoing WGLC. Many thanks to >> those that have reviewed the document and provided their valuable >> feedback -- which has been integrated as best possible into this -06 >> version. >> >> I'd like to ask y'all, and specifically those who were providing >> feedback during WGLC, to quickly review this -06, specifically to >> understand if we can progress the document, or if there are still >> issues that we need to address. I'll note that the WGLC ended on >> September 24, and that this -06 should include all comments received >> during the WGLC. >> >> If you could let your opinion be known on the 'list within >> this week, >> then it'd be very helpful. >> >> Thanks >> >> Thomas >> >> Begin forwarded message: >> >>> From: Internet-Drafts@ietf.org >>> Date: 4October , 2007 11:15:02 PM CEDT >>> To: i-d-announce@ietf.org >>> Cc: autoconf@ietf.org >>> Subject: I-D ACTION:draft-ietf-autoconf-manetarch-06.txt >>> Reply-To: internet-drafts@ietf.org >>> >>> A New Internet-Draft is available from the on-line Internet-Drafts >>> directories. >>> This draft is a work item of the Ad-Hoc Network Autoconfiguration >>> Working Group of the IETF. >>> >>> Title : Mobile Ad hoc Network Architecture >>> Author(s) : I. Chakeres, et al. >>> Filename : draft-ietf-autoconf-manetarch-06.txt >>> Pages : 20 >>> Date : 2007-10-4 >>> >>> 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. >>> >>> A URL for this Internet-Draft is: >>> http://www.ietf.org/internet-drafts/draft-ietf-autoconf- >>> manetarch-06.txt >>> >>> To remove yourself from the I-D Announcement list, send a message to >>> i-d-announce-request@ietf.org with the word unsubscribe in >> the body of >>> the message. >>> You can also visit >> https://www1.ietf.org/mailman/listinfo/I-D-announce >>> to change your subscription settings. >>> >>> Internet-Drafts are also available by anonymous FTP. Login with the >>> username "anonymous" and a password of your e-mail address. After >>> logging in, type "cd internet-drafts" and then >>> "get draft-ietf-autoconf-manetarch-06.txt". >>> >>> A list of Internet-Drafts directories can be found in >>> http://www.ietf.org/shadow.html >>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt >>> >>> Internet-Drafts can also be obtained by e-mail. >>> >>> Send a message to: >>> mailserv@ietf.org. >>> In the body type: >>> "FILE /internet-drafts/draft-ietf-autoconf-manetarch-06.txt". >>> >>> NOTE: The mail server at ietf.org can return the document in >>> MIME-encoded form by using the "mpack" utility. To use this >>> feature, insert the command "ENCODING mime" before the "FILE" >>> command. To decode the response(s), you will need "munpack" or >>> a MIME-compliant mail reader. Different MIME-compliant >> mail readers >>> exhibit different behavior, especially when dealing with >>> "multipart" MIME messages (i.e. documents which have been split >>> up into multiple messages), so check your local documentation on >>> how to manipulate these messages. >>> >>> Below is the data which will enable a MIME compliant mail reader >>> implementation to automatically retrieve the ASCII version of the >>> Internet-Draft. >>> Content-Type: text/plain >>> Content-ID: <2007-10-4163725.I-D@ietf.org> >>> >>> _______________________________________________ >>> I-D-Announce mailing list >>> I-D-Announce@ietf.org >>> https://www1.ietf.org/mailman/listinfo/i-d-announce >> >> -- >> Thomas Clausen >> Thomas@thomasclausen.org >> http://www.thomasclausen.org/ >> http://hipercom.thomasclausen.org/ >> >> >> >> >> _______________________________________________ >> Autoconf mailing list >> Autoconf@ietf.org >> https://www1.ietf.org/mailman/listinfo/autoconf >> > > > _______________________________________________ > Autoconf mailing list > Autoconf@ietf.org > https://www1.ietf.org/mailman/listinfo/autoconf > -- Thomas Clausen Thomas@thomasclausen.org http://www.thomasclausen.org/ http://hipercom.thomasclausen.org/ _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www1.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Mon Oct 08 18:37:05 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1If1Dd-0004iU-Hg; Mon, 08 Oct 2007 18:36:57 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1If1Dc-0004fh-Q8 for autoconf-confirm+ok@megatron.ietf.org; Mon, 08 Oct 2007 18:36:56 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1If1Dc-0004fY-G4 for autoconf@ietf.org; Mon, 08 Oct 2007 18:36:56 -0400 Received: from blv-smtpout-01.boeing.com ([130.76.32.69]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1If1DW-0006yw-6u for autoconf@ietf.org; Mon, 08 Oct 2007 18:36:56 -0400 Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id l98MaIL3016481 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 8 Oct 2007 15:36:23 -0700 (PDT) Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id l98MaIDh006517; Mon, 8 Oct 2007 17:36:18 -0500 (CDT) Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id l98MaE8M006430; Mon, 8 Oct 2007 17:36:17 -0500 (CDT) Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 8 Oct 2007 15:36:15 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Autoconf] Regarding draft-ietf-autoconf-manetarch-06.txt Date: Mon, 8 Oct 2007 15:36:15 -0700 Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029EDB1F@XCH-NW-7V2.nw.nos.boeing.com> In-Reply-To: <6428385A-F072-4AA0-A6B9-631496A1F4E6@polytechnique.fr> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Autoconf] Regarding draft-ietf-autoconf-manetarch-06.txt Thread-Index: AcgJ+3xmum5vluYxR2SGd/C1W8SlGgAAA3/g References: <5F17CFEE-B601-4990-AB62-67E895BFC55C@polytechnique.fr> <39C363776A4E8C4A94691D2BD9D1C9A1029EDB1C@XCH-NW-7V2.nw.nos.boeing.com> <6428385A-F072-4AA0-A6B9-631496A1F4E6@polytechnique.fr> From: "Templin, Fred L" To: "Thomas Clausen" X-OriginalArrivalTime: 08 Oct 2007 22:36:15.0697 (UTC) FILETIME=[A30BF410:01C809FB] X-Spam-Score: -4.0 (----) X-Scan-Signature: 31b28e25e9d13a22020d8b7aedc9832c Cc: autoconf@ietf.org X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: autoconf-bounces@ietf.org How about just strike the word, and we'll move on. Thanks - Fred fred.l.templin@boeing.com=20 > -----Original Message----- > From: Thomas Clausen [mailto:Thomas.Clausen@polytechnique.fr]=20 > Sent: Monday, October 08, 2007 3:35 PM > To: Templin, Fred L > Cc: autoconf@ietf.org > Subject: Re: [Autoconf] Regarding=20 > draft-ietf-autoconf-manetarch-06.txt=20 >=20 > Fred, >=20 > Thanks -- if you have a proposed preferred phrase to replace the one =20 > indicated, then I'm all ears ;) >=20 > Cheers, >=20 > Thomas >=20 > On 8Oct , 2007, at 5:16 PM, Templin, Fred L wrote: >=20 > > Thomas, > > > >> I'd like to ask y'all, and specifically those who were providing > >> feedback during WGLC, to quickly review this -06, > > > > I guess that includes me, and I will do my best to respond > > asap but have a busy week ahead of me. But, one comment for > > now wrt to the "acknowledgements" section: > > > > "While not entirely complete the authors would like to in =20 > > particular > > thank the following individuals for exhaustive discussions and > > valuable contributions:" ^^^^^^^^^^ > > > > I don't quite understand the characterization of "exhaustive"? > > This document has been moved through the process more quickly > > than most (which often undergo intensive scrutiny over the > > course of many years) and I don't see any of them complaining. > > (There wasn't even an issue tracker maintained for this one.) > > Meanwhile, development of the MANET architecture has evloved > > over the course of several decades and I won't even guess as > > to how many vital contributers involved and R&D $'s invested. > > > > It would be good if this could be re-worded. > > > > Fred > > fred.l.templin@boeing.com > > > > > >> -----Original Message----- > >> From: Thomas Clausen [mailto:Thomas.Clausen@polytechnique.fr] > >> Sent: Monday, October 08, 2007 1:00 AM > >> To: autoconf@ietf.org > >> Subject: [Autoconf] Regarding draft-ietf-autoconf-manetarch-06.txt > >> > >> All, > >> > >> As you'll have noted, there have been some comments on the=20 > I-D draft- > >> ietf-autoconf-manetarch as it was undergoing WGLC. Many thanks to > >> those that have reviewed the document and provided their valuable > >> feedback -- which has been integrated as best possible=20 > into this -06 > >> version. > >> > >> I'd like to ask y'all, and specifically those who were providing > >> feedback during WGLC, to quickly review this -06, specifically to > >> understand if we can progress the document, or if there are still > >> issues that we need to address. I'll note that the WGLC ended on > >> September 24, and that this -06 should include all=20 > comments received > >> during the WGLC. > >> > >> If you could let your opinion be known on the 'list within > >> this week, > >> then it'd be very helpful. > >> > >> Thanks > >> > >> Thomas > >> > >> Begin forwarded message: > >> > >>> From: Internet-Drafts@ietf.org > >>> Date: 4October , 2007 11:15:02 PM CEDT > >>> To: i-d-announce@ietf.org > >>> Cc: autoconf@ietf.org > >>> Subject: I-D ACTION:draft-ietf-autoconf-manetarch-06.txt > >>> Reply-To: internet-drafts@ietf.org > >>> > >>> A New Internet-Draft is available from the on-line Internet-Drafts > >>> directories. > >>> This draft is a work item of the Ad-Hoc Network Autoconfiguration > >>> Working Group of the IETF. > >>> > >>> Title : Mobile Ad hoc Network Architecture > >>> Author(s) : I. Chakeres, et al. > >>> Filename : draft-ietf-autoconf-manetarch-06.txt > >>> Pages : 20 > >>> Date : 2007-10-4 > >>> =09 > >>> 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. > >>> > >>> A URL for this Internet-Draft is: > >>> http://www.ietf.org/internet-drafts/draft-ietf-autoconf- > >>> manetarch-06.txt > >>> > >>> To remove yourself from the I-D Announcement list, send a=20 > message to > >>> i-d-announce-request@ietf.org with the word unsubscribe in > >> the body of > >>> the message. > >>> You can also visit > >> https://www1.ietf.org/mailman/listinfo/I-D-announce > >>> to change your subscription settings. > >>> > >>> Internet-Drafts are also available by anonymous FTP.=20 > Login with the > >>> username "anonymous" and a password of your e-mail address. After > >>> logging in, type "cd internet-drafts" and then > >>> "get draft-ietf-autoconf-manetarch-06.txt". > >>> > >>> A list of Internet-Drafts directories can be found in > >>> http://www.ietf.org/shadow.html > >>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > >>> > >>> Internet-Drafts can also be obtained by e-mail. > >>> > >>> Send a message to: > >>> mailserv@ietf.org. > >>> In the body type: > >>> "FILE /internet-drafts/draft-ietf-autoconf-manetarch-06.txt". > >>> =09 > >>> NOTE: The mail server at ietf.org can return the document in > >>> MIME-encoded form by using the "mpack" utility. To use this > >>> feature, insert the command "ENCODING mime" before the "FILE" > >>> command. To decode the response(s), you will need "munpack" or > >>> a MIME-compliant mail reader. Different MIME-compliant > >> mail readers > >>> exhibit different behavior, especially when dealing with > >>> "multipart" MIME messages (i.e. documents which have been split > >>> up into multiple messages), so check your local documentation on > >>> how to manipulate these messages. > >>> > >>> Below is the data which will enable a MIME compliant mail reader > >>> implementation to automatically retrieve the ASCII version of the > >>> Internet-Draft. > >>> Content-Type: text/plain > >>> Content-ID: <2007-10-4163725.I-D@ietf.org> > >>> > >>> _______________________________________________ > >>> I-D-Announce mailing list > >>> I-D-Announce@ietf.org > >>> https://www1.ietf.org/mailman/listinfo/i-d-announce > >> > >> --=20 > >> Thomas Clausen > >> Thomas@thomasclausen.org > >> http://www.thomasclausen.org/ > >> http://hipercom.thomasclausen.org/ > >> > >> > >> > >> > >> _______________________________________________ > >> Autoconf mailing list > >> Autoconf@ietf.org > >> https://www1.ietf.org/mailman/listinfo/autoconf > >> > > > > > > _______________________________________________ > > Autoconf mailing list > > Autoconf@ietf.org > > https://www1.ietf.org/mailman/listinfo/autoconf > > >=20 > --=20 > Thomas Clausen > Thomas@thomasclausen.org > http://www.thomasclausen.org/ > http://hipercom.thomasclausen.org/ >=20 >=20 >=20 _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www1.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Tue Oct 09 02:47:04 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1If8rJ-0006ep-Ju; Tue, 09 Oct 2007 02:46:25 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1If8rH-0006c8-JO for autoconf-confirm+ok@megatron.ietf.org; Tue, 09 Oct 2007 02:46:23 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1If8rD-0006R1-3Q for autoconf@ietf.org; Tue, 09 Oct 2007 02:46:19 -0400 Received: from nf-out-0910.google.com ([64.233.182.185]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1If8r6-0002Zu-6q for autoconf@ietf.org; Tue, 09 Oct 2007 02:46:19 -0400 Received: by nf-out-0910.google.com with SMTP id d21so1057935nfb for ; Mon, 08 Oct 2007 23:45:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=lNdaJWPY3Dl1oIuEfGuRC/bPIl7VpvPEGlZAhu5GhYE=; b=tA9EyzdDWSOqWHQTjpm3oAZt5IWPtcsp3TMpuIhIlN1qQNHV6v3nUlCvFa8JRZ6r6Ww/8Hbzvshzj+X0KT0ssg8Tj9ELQx1qVE1TASEvsCZ/e2Ktkw4DchzPvoLhUuXoEwTj4jIbun/WXHhvmgEWoj6535oowo0V7nZw8Wq6wnA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=cjhX/ptjpXLoC86x/j8pxU50AOyO0jTc8830oK1qh/i68TfVaD3X8EGpMD140Nqv5zEMZa4RhHMIV7K2t9GijryQIpMKXZCbHmjDmdMOaBpX9eZbJa1fB4UoclAIlhf5YMmohsUk/P/4RnmaA8Abu3g/ZJSczdt215KYYwSh1SU= Received: by 10.78.142.14 with SMTP id p14mr11329909hud.1191912325729; Mon, 08 Oct 2007 23:45:25 -0700 (PDT) Received: by 10.78.53.8 with HTTP; Mon, 8 Oct 2007 23:45:25 -0700 (PDT) Message-ID: <374005f30710082345r3d6eea24s1146037b95f626a1@mail.gmail.com> Date: Tue, 9 Oct 2007 12:15:25 +0530 From: "Ian Chakeres" To: "Templin, Fred L" Subject: Re: [Autoconf] Regarding draft-ietf-autoconf-manetarch-06.txt In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1029EDB1F@XCH-NW-7V2.nw.nos.boeing.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <5F17CFEE-B601-4990-AB62-67E895BFC55C@polytechnique.fr> <39C363776A4E8C4A94691D2BD9D1C9A1029EDB1C@XCH-NW-7V2.nw.nos.boeing.com> <6428385A-F072-4AA0-A6B9-631496A1F4E6@polytechnique.fr> <39C363776A4E8C4A94691D2BD9D1C9A1029EDB1F@XCH-NW-7V2.nw.nos.boeing.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: 612a16ba5c5f570bfc42b3ac5606ac53 Cc: autoconf@ietf.org, Thomas Clausen X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: autoconf-bounces@ietf.org I believe I committed a spell-check error. It should read "extensive". I don't know how I miss-spelled extensive to become exhaustive by aspell in emacs, but it happened. Fred, thanks for the thorough (some might say exhaustive) review. Ian On 10/9/07, Templin, Fred L wrote: > How about just strike the word, and we'll move on. > > Thanks - Fred > fred.l.templin@boeing.com > > > -----Original Message----- > > From: Thomas Clausen [mailto:Thomas.Clausen@polytechnique.fr] > > Sent: Monday, October 08, 2007 3:35 PM > > To: Templin, Fred L > > Cc: autoconf@ietf.org > > Subject: Re: [Autoconf] Regarding > > draft-ietf-autoconf-manetarch-06.txt > > > > Fred, > > > > Thanks -- if you have a proposed preferred phrase to replace the one > > indicated, then I'm all ears ;) > > > > Cheers, > > > > Thomas > > > > On 8Oct , 2007, at 5:16 PM, Templin, Fred L wrote: > > > > > Thomas, > > > > > >> I'd like to ask y'all, and specifically those who were providing > > >> feedback during WGLC, to quickly review this -06, > > > > > > I guess that includes me, and I will do my best to respond > > > asap but have a busy week ahead of me. But, one comment for > > > now wrt to the "acknowledgements" section: > > > > > > "While not entirely complete the authors would like to in > > > particular > > > thank the following individuals for exhaustive discussions and > > > valuable contributions:" ^^^^^^^^^^ > > > > > > I don't quite understand the characterization of "exhaustive"? > > > This document has been moved through the process more quickly > > > than most (which often undergo intensive scrutiny over the > > > course of many years) and I don't see any of them complaining. > > > (There wasn't even an issue tracker maintained for this one.) > > > Meanwhile, development of the MANET architecture has evloved > > > over the course of several decades and I won't even guess as > > > to how many vital contributers involved and R&D $'s invested. > > > > > > It would be good if this could be re-worded. > > > > > > Fred > > > fred.l.templin@boeing.com > > > > > > > > >> -----Original Message----- > > >> From: Thomas Clausen [mailto:Thomas.Clausen@polytechnique.fr] > > >> Sent: Monday, October 08, 2007 1:00 AM > > >> To: autoconf@ietf.org > > >> Subject: [Autoconf] Regarding draft-ietf-autoconf-manetarch-06.txt > > >> > > >> All, > > >> > > >> As you'll have noted, there have been some comments on the > > I-D draft- > > >> ietf-autoconf-manetarch as it was undergoing WGLC. Many thanks to > > >> those that have reviewed the document and provided their valuable > > >> feedback -- which has been integrated as best possible > > into this -06 > > >> version. > > >> > > >> I'd like to ask y'all, and specifically those who were providing > > >> feedback during WGLC, to quickly review this -06, specifically to > > >> understand if we can progress the document, or if there are still > > >> issues that we need to address. I'll note that the WGLC ended on > > >> September 24, and that this -06 should include all > > comments received > > >> during the WGLC. > > >> > > >> If you could let your opinion be known on the 'list within > > >> this week, > > >> then it'd be very helpful. > > >> > > >> Thanks > > >> > > >> Thomas > > >> > > >> Begin forwarded message: > > >> > > >>> From: Internet-Drafts@ietf.org > > >>> Date: 4October , 2007 11:15:02 PM CEDT > > >>> To: i-d-announce@ietf.org > > >>> Cc: autoconf@ietf.org > > >>> Subject: I-D ACTION:draft-ietf-autoconf-manetarch-06.txt > > >>> Reply-To: internet-drafts@ietf.org > > >>> > > >>> A New Internet-Draft is available from the on-line Internet-Drafts > > >>> directories. > > >>> This draft is a work item of the Ad-Hoc Network Autoconfiguration > > >>> Working Group of the IETF. > > >>> > > >>> Title : Mobile Ad hoc Network Architecture > > >>> Author(s) : I. Chakeres, et al. > > >>> Filename : draft-ietf-autoconf-manetarch-06.txt > > >>> Pages : 20 > > >>> Date : 2007-10-4 > > >>> > > >>> 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. > > >>> > > >>> A URL for this Internet-Draft is: > > >>> http://www.ietf.org/internet-drafts/draft-ietf-autoconf- > > >>> manetarch-06.txt > > >>> > > >>> To remove yourself from the I-D Announcement list, send a > > message to > > >>> i-d-announce-request@ietf.org with the word unsubscribe in > > >> the body of > > >>> the message. > > >>> You can also visit > > >> https://www1.ietf.org/mailman/listinfo/I-D-announce > > >>> to change your subscription settings. > > >>> > > >>> Internet-Drafts are also available by anonymous FTP. > > Login with the > > >>> username "anonymous" and a password of your e-mail address. After > > >>> logging in, type "cd internet-drafts" and then > > >>> "get draft-ietf-autoconf-manetarch-06.txt". > > >>> > > >>> A list of Internet-Drafts directories can be found in > > >>> http://www.ietf.org/shadow.html > > >>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > >>> > > >>> Internet-Drafts can also be obtained by e-mail. > > >>> > > >>> Send a message to: > > >>> mailserv@ietf.org. > > >>> In the body type: > > >>> "FILE /internet-drafts/draft-ietf-autoconf-manetarch-06.txt". > > >>> > > >>> NOTE: The mail server at ietf.org can return the document in > > >>> MIME-encoded form by using the "mpack" utility. To use this > > >>> feature, insert the command "ENCODING mime" before the "FILE" > > >>> command. To decode the response(s), you will need "munpack" or > > >>> a MIME-compliant mail reader. Different MIME-compliant > > >> mail readers > > >>> exhibit different behavior, especially when dealing with > > >>> "multipart" MIME messages (i.e. documents which have been split > > >>> up into multiple messages), so check your local documentation on > > >>> how to manipulate these messages. > > >>> > > >>> Below is the data which will enable a MIME compliant mail reader > > >>> implementation to automatically retrieve the ASCII version of the > > >>> Internet-Draft. > > >>> Content-Type: text/plain > > >>> Content-ID: <2007-10-4163725.I-D@ietf.org> > > >>> > > >>> _______________________________________________ > > >>> I-D-Announce mailing list > > >>> I-D-Announce@ietf.org > > >>> https://www1.ietf.org/mailman/listinfo/i-d-announce > > >> > > >> -- > > >> Thomas Clausen > > >> Thomas@thomasclausen.org > > >> http://www.thomasclausen.org/ > > >> http://hipercom.thomasclausen.org/ > > >> > > >> > > >> > > >> > > >> _______________________________________________ > > >> Autoconf mailing list > > >> Autoconf@ietf.org > > >> https://www1.ietf.org/mailman/listinfo/autoconf > > >> > > > > > > > > > _______________________________________________ > > > Autoconf mailing list > > > Autoconf@ietf.org > > > https://www1.ietf.org/mailman/listinfo/autoconf > > > > > > > -- > > Thomas Clausen > > Thomas@thomasclausen.org > > http://www.thomasclausen.org/ > > http://hipercom.thomasclausen.org/ > > > > > > > > > _______________________________________________ > Autoconf mailing list > Autoconf@ietf.org > https://www1.ietf.org/mailman/listinfo/autoconf > _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www1.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Wed Oct 10 13:51:21 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IffiE-00057s-Ko; Wed, 10 Oct 2007 13:51:14 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1IffiC-00055g-W7 for autoconf-confirm+ok@megatron.ietf.org; Wed, 10 Oct 2007 13:51:13 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IffiC-00055W-Lt for autoconf@ietf.org; Wed, 10 Oct 2007 13:51:12 -0400 Received: from smtp01.uc3m.es ([163.117.176.131] helo=smtp.uc3m.es) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iffi6-0002TX-5R for autoconf@ietf.org; Wed, 10 Oct 2007 13:51:12 -0400 Received: from [163.117.139.72] (acorde.it.uc3m.es [163.117.139.72]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by smtp.uc3m.es (Postfix) with ESMTP id 4351F14439F; Wed, 10 Oct 2007 19:50:51 +0200 (CEST) From: Carlos =?ISO-8859-1?Q?Jes=FAs?= Bernardos Cano To: autoconf@ietf.org Organization: Universidad Carlos III de Madrid Date: Wed, 10 Oct 2007 19:50:53 +0200 Message-Id: <1192038653.4677.89.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.10.3 X-Spam-Score: 0.0 (/) X-Scan-Signature: 140baa79ca42e6b0e2b4504291346186 Cc: MOUSTAFA Hassnaa RD-CORE-ISS Subject: [Autoconf] [Fwd: I-D Action:draft-bernardos-autoconf-evaluation-considerations-01.txt] X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.5 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="===============1168424925==" Errors-To: autoconf-bounces@ietf.org --===============1168424925== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-ZfibGx1/4WxlSGU755Se" --=-ZfibGx1/4WxlSGU755Se Content-Type: multipart/mixed; boundary="=-Yf6jmiBWqJVUzAp50kp1" --=-Yf6jmiBWqJVUzAp50kp1 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Hi all, We've just submitted a new version of our draft about evaluation consideration for IP autoconf solutions. Comments are welcome. Kind regards, Hassnaa, Mar=EDa and Carlos --=20 =A1AS=D3CIATE! Gratis para estudiantes http://www.telematica.ws Carlos Jes=FAs Bernardos Cano http://www.netcoms.net GPG FP: D29B 0A6A 639A A561 93CA 4D55 35DC BA4D D170 4F67 --=-Yf6jmiBWqJVUzAp50kp1 Content-Disposition: inline Content-Description: Mensaje reenviado: I-D Action:draft-bernardos-autoconf-evaluation-considerations-01.txt Content-Type: message/rfc822 Return-Path: Received: from smtp.uc3m.es (smtp02.uc3m.es [163.117.176.132]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by shem.uc3m.es (Postfix) with ESMTP id 90920124E5; Wed, 10 Oct 2007 19:48:00 +0200 (CEST) Received: from megatron.ietf.org (odin.ietf.ORG [156.154.16.145])(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))(No client certificate requested)by smtp.uc3m.es (Postfix) with ESMTP id 23E911343FA; Wed, 10 Oct 2007 19:47:59 +0200 (CEST) Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)by megatron.ietf.org with esmtp (Exim 4.43) id 1IffNt-0004hk-6Yfor i-d-announce@ietf.org; Wed, 10 Oct 2007 13:30:13 -0400 Received: from ns3.neustar.com ([156.154.24.138])by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IffNs-0003vI-PZfor i-d-announce@ietf.org; Wed, 10 Oct 2007 13:30:13 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 792DA175C0for ; Wed, 10 Oct 2007 17:30:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)id 1IffNi-000596-0wfor i-d-announce@ietf.org; Wed, 10 Oct 2007 13:30:02 -0400 Content-Type: Multipart/Mixed; Boundary=NextPart Mime-Version: 1.0 To: i-d-announce@ietf.org Cc: From: Internet-Drafts@ietf.org Message-Id: Date: Wed, 10 Oct 2007 13:30:02 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be Subject: I-D Action:draft-bernardos-autoconf-evaluation-considerations-01.txt X-BeenThere: i-d-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: internet-drafts@ietf.org List-Id: i-d-announce.ietf.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: i-d-announce-bounces@ietf.org X-imss-version: 2.048 X-imss-result: Passed X-imss-scanInfo: M:B L:N SM:2 X-imss-tmaseResult: TT:1 TS:-11.8027 TC:1F TRN:66 TV:5.0.1023(15476.000) X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0 X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000) --NextPart Content-Transfer-Encoding: quoted-printable A New Internet-Draft is available from the on-line Internet-Drafts director= ies. Title : Evaluation Considerations for IP Autoconfiguration Mecha= nisms in MANETs Author(s) : H. Moustafa, et al. Filename : draft-bernardos-autoconf-evaluation-considerations-01.tx= t Pages : 12 Date : 2007-10-10 This Internet Draft aims at providing general guidelines for the AUTOCONF solution space, through providing a set of evaluation considerations for IP autoconfiguration mechanisms in MANETs. These evaluation considerations conform to the AUTOCONF problem statement draft and the MANET architecture draft. The main objective of this draft is to illustrate some key features and highlight some important behaviours for the different autoconf mechanisms, and thus aiming to help solution developers during mechanisms' design and to help implementers in the choice of the autoconf mechanism that fits better their particular requirements, taking into consideration a number of important factors that are discussed in this draft. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-bernardos-autoconf-evaluation-con= siderations-01.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of=20 the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the=20 username "anonymous" and a password of your e-mail address. After=20 logging in, type "cd internet-drafts" and then "get draft-bernardos-autoconf-evaluation-considerations-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-bernardos-autoconf-evaluation-considerations-= 01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Transfer-Encoding: quoted-printable Content-Type: text/plain Content-ID: <2007-10-10132941.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-bernardos-autoconf-evaluation-considerations-01= .txt --OtherAccess Content-Type: Message/External-body; name="draft-bernardos-autoconf-evaluation-considerations-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Transfer-Encoding: quoted-printable Content-Type: text/plain Content-ID: <2007-10-10132941.I-D\@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce --NextPart-- --=-Yf6jmiBWqJVUzAp50kp1-- --=-ZfibGx1/4WxlSGU755Se 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.6 (GNU/Linux) iD8DBQBHDRD9Ndy6TdFwT2cRAjGHAKDhOehFgNcCEAhJSAFbdDWU6dcrKgCgvFeW JDtJ2EYxholk7/UcB3dbc2o= =r7Vs -----END PGP SIGNATURE----- --=-ZfibGx1/4WxlSGU755Se-- --===============1168424925== 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://www1.ietf.org/mailman/listinfo/autoconf --===============1168424925==-- From autoconf-bounces@ietf.org Wed Oct 24 09:21:46 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkgAu-0004Aa-Iu; Wed, 24 Oct 2007 09:21:32 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1IkgAt-0004AN-Eh for autoconf-confirm+ok@megatron.ietf.org; Wed, 24 Oct 2007 09:21:31 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkgAt-0004AB-1P for autoconf@ietf.org; Wed, 24 Oct 2007 09:21:31 -0400 Received: from outbound.mailhop.org ([63.208.196.171]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IkgAm-0005EP-S8 for autoconf@ietf.org; Wed, 24 Oct 2007 09:21:30 -0400 Received: from aste-genev-bois-153-1-21-233.w83-112.abo.wanadoo.fr ([83.112.201.233] helo=[192.168.147.106]) by outbound.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1IkgAX-00013o-D4 for autoconf@ietf.org; Wed, 24 Oct 2007 09:21:09 -0400 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 83.112.201.233 X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/AaQzv+6VLi2/wd0xEjxVy Mime-Version: 1.0 (Apple Message framework v752.3) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: autoconf@ietf.org From: Thomas Clausen Date: Wed, 24 Oct 2007 15:21:06 +0200 X-Mailer: Apple Mail (2.752.3) X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Subject: [Autoconf] draft-ietf-autoconf-manetarch-06.txt X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: autoconf-bounces@ietf.org Dear all, It's been about 2 weeks since the -06 of the I-D in subj was posted, and other than Freds good remark there have been no other comments to this version of the I-D on the list. I'd like to recall that a WGLC has ended on this I-D, and so we should be moving the document forward if we're happy with it. I'm tempted to interpret silence as "yes, we're happy with it", but please do speak up either way. With the hope that we can move this I-D forward before Vancouver, Thomas -- Thomas Clausen Thomas@thomasclausen.org http://www.thomasclausen.org/ http://hipercom.thomasclausen.org/ _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www1.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Thu Oct 25 05:05:24 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ikydw-0000R1-PZ; Thu, 25 Oct 2007 05:04:44 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1Ikydw-0000Qt-AK for autoconf-confirm+ok@megatron.ietf.org; Thu, 25 Oct 2007 05:04:44 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ikydv-0000Qf-L7 for autoconf@ietf.org; Thu, 25 Oct 2007 05:04:43 -0400 Received: from mail153.messagelabs.com ([216.82.253.51]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Ikydp-0004Rv-EI for autoconf@ietf.org; Thu, 25 Oct 2007 05:04:43 -0400 X-VirusChecked: Checked X-Env-Sender: alexandru.petrescu@gmail.com X-Msg-Ref: server-11.tower-153.messagelabs.com!1193303041!12826398!1 X-StarScan-Version: 5.5.12.14.2; banners=.,-,- X-Originating-IP: [144.189.100.101] Received: (qmail 13614 invoked from network); 25 Oct 2007 09:04:01 -0000 Received: from motgate2.mot.com (HELO motgate2.mot.com) (144.189.100.101) by server-11.tower-153.messagelabs.com with SMTP; 25 Oct 2007 09:04:01 -0000 Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233]) by motgate2.mot.com (8.12.11/Motorola) with ESMTP id l9P93t0F015150; Thu, 25 Oct 2007 02:03:55 -0700 (MST) Received: from az10vts02.mot.com (az10vts02.mot.com [10.64.251.243]) by az33exr03.mot.com (8.13.1/Vontu) with SMTP id l9P93scE019824; Thu, 25 Oct 2007 04:03:55 -0500 (CDT) Received: from [127.0.0.1] (zfr01-2117.crm.mot.com [10.161.201.117]) by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id l9P93qw9019808; Thu, 25 Oct 2007 04:03:53 -0500 (CDT) Message-ID: <47205BF8.6070409@gmail.com> Date: Thu, 25 Oct 2007 11:03:52 +0200 From: Alexandru Petrescu User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Thomas Clausen Subject: Re: [Autoconf] draft-ietf-autoconf-manetarch-06.txt References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 000783-1, 22/10/2007), Outbound message X-Antivirus-Status: Clean X-CFilter-Loop: Reflected X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Cc: autoconf@ietf.org X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: autoconf-bounces@ietf.org I'm tempted to speak up but I don't know what to say. For one, I feel the urge to advance the document and, generally speaking, I'm very supportive about the ideas in the document. Thus, I can easily say - yes I'm happy with it. But then, looking at section 5.1 General Address Architecture: -I can't parse the figure: where are the interfaces precisely? Is the loopback assigned P:1::/64? -"MANET interfaces are specifically *NOT* configured with this prefix.": which prefix? The previous paragraph mentions at least two prefixes. -what's the difference between "assigned" and "delegated" prefix? The picture seems to make a distinction, but I don't understand. Also, the paragraph should also let the MANET Router have completely different prefixes on their interfaces. Currently, the paragraph says that there should be (eg) a common P::/62 out of which (eg) P:1::/64 and P:2::/64 are assigned on two different interfaces. This is an example ok. But there should also be a possibility of eg Q::/64 and R::/64 on two different interfaces, Q and R having only the first three bits common (001), and without needing to have 001::/64 "delegated" to the MANET router. Otherwise - yes, I'm fine with the document. Alex PS: I hope I'm not exhausting the authors with these comments :-) Thomas Clausen wrote: > Dear all, > > It's been about 2 weeks since the -06 of the I-D in subj was posted, and > other than Freds good remark there have been no other comments to this > version of the I-D on the list. > > I'd like to recall that a WGLC has ended on this I-D, and so we should > be moving the document forward if we're happy with it. I'm tempted to > interpret silence as "yes, we're happy with it", but please do speak up > either way. > > With the hope that we can move this I-D forward before Vancouver, > > Thomas > > ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www1.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Thu Oct 25 11:30:12 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Il4ee-0004A5-Eg; Thu, 25 Oct 2007 11:29:52 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1Il4ec-00048d-Rq for autoconf-confirm+ok@megatron.ietf.org; Thu, 25 Oct 2007 11:29:50 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Il4ec-00041n-Hg for autoconf@ietf.org; Thu, 25 Oct 2007 11:29:50 -0400 Received: from smtprelay03.ispgateway.de ([80.67.18.15]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Il4eS-0008Ao-An for autoconf@ietf.org; Thu, 25 Oct 2007 11:29:46 -0400 Received: (qmail 30933 invoked from network); 25 Oct 2007 15:29:21 -0000 Received: from unknown (HELO 0-007.vpn.RWTH-Aachen.DE) (159037@[134.130.240.7]) (envelope-sender ) by smtprelay03.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 25 Oct 2007 15:29:21 -0000 From: Volker =?iso-8859-1?q?B=F6hme?= To: autoconf@ietf.org Date: Thu, 25 Oct 2007 17:29:06 +0200 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200710251729.06666.mailinglisten@volker-boehme.de> X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Subject: [Autoconf] Effect of IP assignment on routing X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: autoconf-bounces@ietf.org Hello, i am searching for some Information about how autoconfiguration of IP=20 addresses effects routing. Unfortunately i didn't find any paper which=20 addresses such problem. So does one of you know a paper which includes some= =20 information about the effect of IP assignment on routing? Please inform me = if=20 you know one. kind regards, Volker B=F6hme _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www1.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Thu Oct 25 20:22:39 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IlCxk-0003gR-4o; Thu, 25 Oct 2007 20:22:08 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1IlCxi-0003Nl-Pk for autoconf-confirm+ok@megatron.ietf.org; Thu, 25 Oct 2007 20:22:06 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IlCxi-0003G6-4R for autoconf@ietf.org; Thu, 25 Oct 2007 20:22:06 -0400 Received: from rv-out-0910.google.com ([209.85.198.185]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IlCxb-0003Kd-9H for autoconf@ietf.org; Thu, 25 Oct 2007 20:22:06 -0400 Received: by rv-out-0910.google.com with SMTP id l15so569694rvb for ; Thu, 25 Oct 2007 17:21:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:mime-version:content-type; bh=REWoo2BlpnpQAFwMngYiRIFpgCCy6QxRh1VAX5Oy/Ys=; b=BLSixS7AHBWoKG3FE6fCNwIGpgw3g1zY5JQ93WSJtZBBWXxN9JXhQT2dvZSRpHJMgW8JYqfwArNTfbp0s3lMooRr1MYUfp54xXgK3927Rx50frILO8qqPUaDMppJ0VOo+F4juTVs1XGyi8nPJbuEkefPoNDIxHLT7uHfcB2OPFA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:mime-version:content-type; b=uKGUaUQctgmnGJYVaC8RfjE9Ahkto00EH+UWSh3S7xsuCg65qPN1b9XSIwSyyL9pH29mUl0RvmyWV4lnBwk0Wkchr3tIbsP3MltHerJJGv8PvTM7n/rhpRbO0jAWeb3ZupktlKb9Gprtwo+QbKgtykedm+99o6WOgzxPBQb+8d4= Received: by 10.142.88.20 with SMTP id l20mr754940wfb.1193358092629; Thu, 25 Oct 2007 17:21:32 -0700 (PDT) Received: by 10.143.33.8 with HTTP; Thu, 25 Oct 2007 17:21:32 -0700 (PDT) Message-ID: <7e8d02d40710251721q4e3b5bf4y43b9ae2dcf777721@mail.gmail.com> Date: Fri, 26 Oct 2007 09:21:32 +0900 From: "HyungJin Lim" To: mailinglisten@volker-boehme.de Subject: RE: [Autoconf] Effect of IP assignment on routing MIME-Version: 1.0 X-Spam-Score: 0.0 (/) X-Scan-Signature: 34d35111647d654d033d58d318c0d21a Cc: autoconf@ietf.org X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.5 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="===============0017154813==" Errors-To: autoconf-bounces@ietf.org --===============0017154813== Content-Type: multipart/alternative; boundary="----=_Part_4819_14027440.1193358092621" ------=_Part_4819_14027440.1193358092621 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline hi volker bohme Let's consider Internet connectivity, the one of important elements is whether topological correct address(TCA) can be configured within MANET are= a I think. If any MANET node has TCA scheme, a packet could required a forwarding mechanism such tunneling or IPv6 routing extention header to transfer its own to internet, otherwise a packet could use route entry configured by any routing protocol to internet. IP assignment within only MANET area is another problem I think So I think there are various views according to viewpoint. How about think my opinion ? best regards Hyung-Jin, Lim ----- Original Message ----- From: "Volker B=F6hme" To: Sent: Friday, October 26, 2007 12:29 AM Subject: [Autoconf] Effect of IP assignment on routing > Hello, > > i am searching for some Information about how autoconfiguration of IP > addresses effects routing. Unfortunately i didn't find any paper which > addresses such problem. So does one of you know a paper which includes some > information about the effect of IP assignment on routing? Please inform m= e if > you know one. > > kind regards, > Volker B=F6hme > > > _______________________________________________ > Autoconf mailing list > Autoconf@ietf.org > https://www1.ietf.org/mailman/listinfo/autoconf > > ------=_Part_4819_14027440.1193358092621 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline hi volker bohme

Let's consider Internet connectivity, the one of= important elements is whether topological correct address(TCA) can be conf= igured within MANET area I think.
If any MANET node has TCA scheme, a pa= cket could required a forwarding mechanism such tunneling or IPv6 rout= ing extention header to transfer its own to internet,=20
otherwise a packet could use route entry configured by any routing prot= ocol to internet.

IP assignment within only MANET area is another pr= oblem I think

So I think there are various views according to viewpo= int.=20

How about think my opinion ?

best regards
Hyung-Jin, Lim=

----- Original Message -----
From: "Volker B=F6hme" &= lt; mailinglisten@volker-boehme.de >
To: <autoconf@ietf.org>
Sent: Friday, October 26, 2007 12= :29 AM
Subject: [Autoconf] Effect of IP assignment on routing


> = Hello,
>
> i am searching for some Information about how autoc= onfiguration of IP
> addresses effects routing. Unfortunately i didn= 't find any paper which=20
> addresses such problem. So does one of you know a paper which incl= udes some
> information about the effect of IP assignment on routing= ? Please inform me if
> you know one.
>
> kind regards,
> Volker B=F6hme
>
>
> _________________________= ______________________
> Autoconf mailing list
> Autoconf@ietf.org
> https://www1.ietf.org/mailman/listinfo/autoconf
> =
>=20 ------=_Part_4819_14027440.1193358092621-- --===============0017154813== 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://www1.ietf.org/mailman/listinfo/autoconf --===============0017154813==-- From autoconf-bounces@ietf.org Fri Oct 26 01:15:25 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IlHXJ-0005sC-NW; Fri, 26 Oct 2007 01:15:09 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1IlCPV-00087T-Qn for autoconf-confirm+ok@megatron.ietf.org; Thu, 25 Oct 2007 19:46:45 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1IlCPV-00087L-HU for autoconf@ietf.org; Thu, 25 Oct 2007 19:46:45 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IlCNH-0005Ot-Tj for autoconf@ietf.org; Thu, 25 Oct 2007 19:44:27 -0400 Received: from [211.168.23.25] (helo=fsaspam.fsa.or.kr) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IlCNC-0002Oh-N4 for autoconf@ietf.org; Thu, 25 Oct 2007 19:44:23 -0400 Received: from [10.10.10.55] ([10.10.10.55]) by fsaspam.fsa.or.kr ([211.168.23.25]) with ESMTP id 1193355771.539786.3051215792.fsaspam for <>; Fri, 26 Oct 2007 08:42:51 +0900 (KST) Message-ID: <025301c81760$f9723590$370a0a0a@HP17039251939> From: "???\(FSA\)" To: =?iso-8859-1?Q?Volker_B=F6hme?= References: <200710251729.06666.mailinglisten@volker-boehme.de> Subject: Re: [Autoconf] Effect of IP assignment on routing X-TERRACE-DUMMYSUBJECT: Terrace Spam system * Date: Fri, 26 Oct 2007 08:44:13 +0900 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-TERRACE-SPAMMARK: NO (SR:18.41) (by Terrace) X-TERRACE-CLASSID: type=NO, str=0001.0A090204.472129CA.011E, ss=1, fgs=0 X-Spam-Score: 2.9 (++) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a X-TMDA-Confirmed: Thu, 25 Oct 2007 19:46:45 -0400 X-Mailman-Approved-At: Fri, 26 Oct 2007 01:15:08 -0400 Cc: autoconf@ietf.org, ??? X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.5 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="===============0339095404==" Errors-To: autoconf-bounces@ietf.org --===============0339095404== Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: base64 aGkgdm9sa2VyIGJvaG1lDQoNCkxldCdzIGNvbnNpZGVyIEludGVybmV0IGNvbm5lY3Rpdml0eSwg dGhlIG9uZSBvZiBpbXBvcnRhbnQgZWxlbWVudHMgaXMgd2hldGhlciB0b3BvbG9naWNhbCBjb3Jy ZWN0IGFkZHJlc3MoVENBKSBjYW4gYmUgY29uZmlndXJlZCB3aXRoaW4gTUFORVQgYXJlYSBJIHRo aW5rLg0KSWYgYW55IE1BTkVUIG5vZGUgaGFzIFRDQSBzY2hlbWUsIGEgcGFja2V0IGNvdWxkIGJl IHJlcXVpcmVkIGEgZm9yd2FyZGluZyBtZWNoYW5pc20gdG8gdHJhc2ZlciBpdHMgb3duIHRvIGlu dGVybmV0LA0Kb3RoZXJ3aXNlIGEgcGFja2V0IGNvdWxkIHVzZSByb3V0ZSBlbnRyeSBjb25maWd1 cmVkIGJ5IGFueSByb3V0aW5nIHByb3RvY29sIHRvIGludGVybmV0Lg0KDQpJUCBhc3NpZ25tZW50 IHdpdGhpbiBvbmx5IE1BTkVUIGFyZWEgaXMgYW5vdGhlciBwcm9ibGVtIEkgdGhpbmsNCg0KU28g SSB0aGluayB0aGVyZSBhcmUgdmFyaW91cyB2aWV3cyBhY2NvcmRpbmcgdG8gdmlld3BvaW50Lg0K DQpIb3cgYWJvdXQgdGhpbmsgbXkgb3BpbmlvbiA/IA0KDQpiZXN0IHJlZ2FyZHMNCkh5dW5nLUpp biwgTGltDQoNCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0gDQpGcm9tOiAiVm9sa2VyIEL2 aG1lIiA8bWFpbGluZ2xpc3RlbkB2b2xrZXItYm9laG1lLmRlPg0KVG86IDxhdXRvY29uZkBpZXRm Lm9yZz4NClNlbnQ6IEZyaWRheSwgT2N0b2JlciAyNiwgMjAwNyAxMjoyOSBBTQ0KU3ViamVjdDog W0F1dG9jb25mXSBFZmZlY3Qgb2YgSVAgYXNzaWdubWVudCBvbiByb3V0aW5nDQoNCg0KPiBIZWxs bywNCj4gDQo+IGkgYW0gc2VhcmNoaW5nIGZvciBzb21lIEluZm9ybWF0aW9uIGFib3V0IGhvdyBh dXRvY29uZmlndXJhdGlvbiBvZiBJUCANCj4gYWRkcmVzc2VzIGVmZmVjdHMgcm91dGluZy4gVW5m b3J0dW5hdGVseSBpIGRpZG4ndCBmaW5kIGFueSBwYXBlciB3aGljaCANCj4gYWRkcmVzc2VzIHN1 Y2ggcHJvYmxlbS4gU28gZG9lcyBvbmUgb2YgeW91IGtub3cgYSBwYXBlciB3aGljaCBpbmNsdWRl cyBzb21lIA0KPiBpbmZvcm1hdGlvbiBhYm91dCB0aGUgZWZmZWN0IG9mIElQIGFzc2lnbm1lbnQg b24gcm91dGluZz8gUGxlYXNlIGluZm9ybSBtZSBpZiANCj4geW91IGtub3cgb25lLg0KPiANCj4g a2luZCByZWdhcmRzLA0KPiBWb2xrZXIgQvZobWUNCj4gDQo+IA0KPiBfX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBBdXRvY29uZiBtYWlsaW5nIGxpc3QN Cj4gQXV0b2NvbmZAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlz dGluZm8vYXV0b2NvbmYNCj4gDQo+ --===============0339095404== 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://www1.ietf.org/mailman/listinfo/autoconf --===============0339095404==-- From autoconf-bounces@ietf.org Fri Oct 26 05:39:31 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IlLem-0001yg-GY; Fri, 26 Oct 2007 05:39:08 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1IlLej-0001xg-CW for autoconf-confirm+ok@megatron.ietf.org; Fri, 26 Oct 2007 05:39:05 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IlLej-0001ub-0F for autoconf@ietf.org; Fri, 26 Oct 2007 05:39:05 -0400 Received: from mail153.messagelabs.com ([216.82.253.51]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IlLea-0003ZN-Gb for autoconf@ietf.org; Fri, 26 Oct 2007 05:38:56 -0400 X-VirusChecked: Checked X-Env-Sender: alexandru.petrescu@gmail.com X-Msg-Ref: server-9.tower-153.messagelabs.com!1193391535!6401073!1 X-StarScan-Version: 5.5.12.14.2; banners=.,-,- X-Originating-IP: [129.188.136.8] Received: (qmail 27113 invoked from network); 26 Oct 2007 09:38:55 -0000 Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-9.tower-153.messagelabs.com with SMTP; 26 Oct 2007 09:38:55 -0000 Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l9Q9coKP021928; Fri, 26 Oct 2007 02:38:55 -0700 (MST) Received: from il06vts04.mot.com (il06vts04.mot.com [129.188.137.144]) by il06exr04.mot.com (8.13.1/Vontu) with SMTP id l9Q9covi002737; Fri, 26 Oct 2007 04:38:50 -0500 (CDT) Received: from [127.0.0.1] (zfr01-2117.crm.mot.com [10.161.201.117]) by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id l9Q9cm9Y002723; Fri, 26 Oct 2007 04:38:49 -0500 (CDT) Message-ID: <4721B5A8.9020104@gmail.com> Date: Fri, 26 Oct 2007 11:38:48 +0200 From: Alexandru Petrescu User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: =?ISO-8859-1?Q?Volker_B=F6hme?= Subject: Re: [Autoconf] Effect of IP assignment on routing References: <200710251729.06666.mailinglisten@volker-boehme.de> In-Reply-To: <200710251729.06666.mailinglisten@volker-boehme.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Antivirus: avast! (VPS 071025-1, 25/10/2007), Outbound message X-Antivirus-Status: Clean X-CFilter-Loop: Reflected X-Spam-Score: 0.0 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Cc: autoconf@ietf.org X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: autoconf-bounces@ietf.org Volker Böhme wrote: > Hello, > > i am searching for some Information about how autoconfiguration of IP > addresses effects routing. Information may be closer to you than you may doubt :-) Auto-configuring an IPv4 address on a endhost with DHCPv4 involves adding a default route and a 'connected' route in that host's routing table. One can check that with ifconfig and route or netstat commands. Auto-configuring an IPv6 address with stateless auto-config involves the same. I _think_ DHCPv6 Prefix Delegation (assign a prefix to a end node, not an address) involves adding routes on the remote systems (not on the end node), but I have never tried in practice. Same if you try PPP. > Unfortunately i didn't find any paper which addresses such problem. This is a bit normal. Normally, assigning an address to a node always respects the pre-established addressing topology; routing is not supposed to change upon address assignment. Unless of course we talk alternative or different Internet designs, or micro-mobility, or MANETs. For all these there's a large body of publications, Internet Drafts and patents. I'm not sure what you look for exactly. And if you don't find one - write one :-) What do you want to write? Alex ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www1.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Fri Oct 26 10:58:37 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IlQdl-0001n3-N5; Fri, 26 Oct 2007 10:58:25 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1IlQdj-0001eu-RC for autoconf-confirm+ok@megatron.ietf.org; Fri, 26 Oct 2007 10:58:23 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IlQdj-0001c7-FN for autoconf@ietf.org; Fri, 26 Oct 2007 10:58:23 -0400 Received: from stl-smtpout-01.boeing.com ([130.76.96.56]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IlQdj-00059j-6H for autoconf@ietf.org; Fri, 26 Oct 2007 10:58:23 -0400 Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id l9QEwBm8014660 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 26 Oct 2007 09:58:11 -0500 (CDT) Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id l9QEwBeS011499; Fri, 26 Oct 2007 09:58:11 -0500 (CDT) Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id l9QEvx8D011027; Fri, 26 Oct 2007 09:58:00 -0500 (CDT) Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 26 Oct 2007 07:57:56 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Autoconf] Effect of IP assignment on routing Date: Fri, 26 Oct 2007 07:57:56 -0700 Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029EDB85@XCH-NW-7V2.nw.nos.boeing.com> In-Reply-To: <4721B5A8.9020104@gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Autoconf] Effect of IP assignment on routing Thread-Index: AcgXtO/gv99CDxxvTayzNiTkaVSwYgAKy2Mg References: <200710251729.06666.mailinglisten@volker-boehme.de> <4721B5A8.9020104@gmail.com> From: "Templin, Fred L" To: "Alexandru Petrescu" , =?iso-8859-1?Q?Volker_B=F6hme?= X-OriginalArrivalTime: 26 Oct 2007 14:57:56.0738 (UTC) FILETIME=[97D34E20:01C817E0] X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Cc: autoconf@ietf.org X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: autoconf-bounces@ietf.org Alex,=20 =20 > I _think_ DHCPv6 Prefix Delegation (assign a prefix to a end node, not > an address) involves adding routes on the remote systems (not on the = end > node), but I have never tried in practice. I want to also allow DHCPv6 PD for /128 prefixes (i.e., a singleton prefix) which is pretty much the same thing as an address. I have checked specs and talked to authors, and AFAICT DHCPv6 PD supports delegation of /128s. Thanks - Fred fred.l.templin@boeing.com=20 _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www1.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Tue Oct 30 06:53:43 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Imoip-0000to-PZ; Tue, 30 Oct 2007 06:53:23 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1Imoin-0000tV-DI for autoconf-confirm+ok@megatron.ietf.org; Tue, 30 Oct 2007 06:53:21 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Imoin-0000si-2c for autoconf@ietf.org; Tue, 30 Oct 2007 06:53:21 -0400 Received: from smtprelay06.ispgateway.de ([80.67.18.44]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Imoih-0006Xm-F3 for autoconf@ietf.org; Tue, 30 Oct 2007 06:53:15 -0400 Received: (qmail 6257 invoked from network); 30 Oct 2007 10:53:14 -0000 Received: from unknown (HELO 3-036.vpn.RWTH-Aachen.DE) (159037@[134.130.243.36]) (envelope-sender ) by smtprelay06.ispgateway.de (qmail-ldap-1.03) with SMTP; 30 Oct 2007 10:53:14 -0000 From: Volker =?utf-8?q?B=C3=B6hme?= Subject: Re: [Autoconf] Effect of IP assignment on routing Date: Tue, 30 Oct 2007 11:53:13 +0100 User-Agent: KMail/1.9.7 References: <7e8d02d40710251721q4e3b5bf4y43b9ae2dcf777721@mail.gmail.com> In-Reply-To: <7e8d02d40710251721q4e3b5bf4y43b9ae2dcf777721@mail.gmail.com> MIME-Version: 1.0 Content-Disposition: inline X-Length: 1599 X-UID: 42 To: "HyungJin Lim" Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <200710301153.13678.mailinglisten@volker-boehme.de> X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Cc: autoconf@ietf.org X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: autoconf-bounces@ietf.org Hello HyungJin Lim, i really dont understand what you are trying to tell me. Perhaps i wasn't = =09 accurate enough and you also dont understand me. The scenario i was looking= =20 it is as follows:=20 1. We have a MANET with Internet connectivity. 2. IP Address should be assigned to each node. 3. An ad-hoc routing protocol is used within the MANET. Now there are different possibilities which routing protocol can be used.=20 There are routing protocols which use flat routing (AODV,OLSR) and there ar= e=20 routing protocols which use hierarchical routing (ZRP, HARP). My question= =20 know is, if there are any studies about the effect of used autoconfiguratio= n=20 algorithm regarding to the used routing protocol. How does the=20 autoconfiguration algorithm effect the routing tabels?=20 kind regards Volker B=C3=B6hme _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www1.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Tue Oct 30 06:53:43 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Imoip-0000th-0a; Tue, 30 Oct 2007 06:53:23 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1Imoin-0000tU-Cw for autoconf-confirm+ok@megatron.ietf.org; Tue, 30 Oct 2007 06:53:21 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Imoin-0000sV-2e for autoconf@ietf.org; Tue, 30 Oct 2007 06:53:21 -0400 Received: from smtprelay03.ispgateway.de ([80.67.18.15]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Imoie-0006Xc-B3 for autoconf@ietf.org; Tue, 3From autoconf-bounces@ietf.org Tue Oct 30 06:53:43 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Imoip-0000to-PZ; Tue, 30 Oct 2007 06:53:23 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1Imoin-0000tV-DI for autoconf-confirm+ok@megatron.ietf.org; Tue, 30 Oct 2007 06:53:21 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Imoin-0000si-2c for autoconf@ietf.org; Tue, 30 Oct 2007 06:53:21 -0400 Received: from smtprelay06.ispgateway.de ([80.67.18.44]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Imoih-0006Xm-F3 for autoconf@ietf.org; Tue, 30 Oct 2007 06:53:15 -0400 Received: (qmail 6257 invoked from network); 30 Oct 2007 10:53:14 -0000 Received: from unknown (HELO 3-036.vpn.RWTH-Aachen.DE) (159037@[134.130.243.36]) (envelope-sender ) by smtprelay06.ispgateway.de (qmail-ldap-1.03) with SMTP; 30 Oct 2007 10:53:14 -0000 From: Volker =?utf-8?q?B=C3=B6hme?= Subject: Re: [Autoconf] Effect of IP assignment on routing Date: Tue, 30 Oct 2007 11:53:13 +0100 User-Agent: KMail/1.9.7 References: <7e8d02d40710251721q4e3b5bf4y43b9ae2dcf777721@mail.gmail.com> In-Reply-To: <7e8d02d40710251721q4e3b5bf4y43b9ae2dcf777721@mail.gmail.com> MIME-Version: 1.0 Content-Disposition: inline X-Length: 1599 X-UID: 42 To: "HyungJin Lim" Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <200710301153.13678.mailinglisten@volker-boehme.de> X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Cc: autoconf@ietf.org X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: autoconf-bounces@ietf.org Hello HyungJin Lim, i really dont understand what you are trying to tell me. Perhaps i wasn't = =09 accurate enough and you also dont understand me. The scenario i was looking= =20 it is as follows:=20 1. We have a MANET with Internet connectivity. 2. IP Address should be assigned to each node. 3. An ad-hoc routing protocol is used within the MANET. Now there are different possibilities which routing protocol can be used.=20 There are routing protocols which use flat routing (AODV,OLSR) and there ar= e=20 routing protocols which use hierarchical routing (ZRP, HARP). My question= =20 know is, if there are any studies about the effect of used autoconfiguratio= n=20 algorithm regarding to the used routing protocol. How does the=20 autoconfiguration algorithm effect the routing tabels?=20 kind regards Volker B=C3=B6hme _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www1.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Tue Oct 30 06:53:43 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Imoip-0000th-0a; Tue, 30 Oct 2007 06:53:23 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1Imoin-0000tU-Cw for autoconf-confirm+ok@megatron.ietf.org; Tue, 30 Oct 2007 06:53:21 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Imoin-0000sV-2e for autoconf@ietf.org; Tue, 30 Oct 2007 06:53:21 -0400 Received: from smtprelay03.ispgateway.de ([80.67.18.15]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Imoie-0006Xc-B3 for autoconf@ietf.org; Tue, 30 Oct 2007 06:53:12 -0400 Received: (qmail 4065 invoked from network); 30 Oct 2007 10:53:11 -0000 Received: from unknown (HELO 3-036.vpn.RWTH-Aachen.DE) (159037@[134.130.243.36]) (envelope-sender ) by smtprelay03.ispgateway.de (qmail-ldap-1.03) with SMTP; 30 Oct 2007 10:53:11 -0000 From: Volker =?iso-8859-1?q?B=F6hme?= To: Alexandru Petrescu Subject: Re: [Autoconf] Effect of IP assignment on routing Date: Tue, 30 Oct 2007 11:53:09 +0100 User-Agent: KMail/1.9.7 References: <200710251729.06666.mailinglisten@volker-boehme.de> <4721B5A8.9020104@gmail.com> In-Reply-To: <4721B5A8.9020104@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200710301153.09747.mailinglisten@volker-boehme.de> X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Cc: autoconf@ietf.org X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: autoconf-bounces@ietf.org Hi Alex, what you are talking about is not really what i had in mind. The scenario i= =20 was looking at it is as follows:=20 1. We have a MANET with Internet connectivity. 2. IP Address should be assigned to each node. 3. An ad-hoc routing protocol is used within the MANET. Now there are different possibilities which routing protocol can be used.=20 There are routing protocols which use flat routing (AODV,OLSR) and there ar= e=20 routing protocols which use hierarchical routing (ZRP, HARP). My question= =20 know is, if there are any studies about the effect of used autoconfiguratio= n=20 algorithm regarding to the used routing protocol. How does the=20 autoconfiguration algorithm effect the routing tabels? On Friday 26 October 2007 11:38:48 you wrote: > This is a bit normal. Normally, assigning an address to a node always > respects the pre-established addressing topology; routing is not > supposed to change upon address assignment. But the routing tables depend on how the address are assigned. So can the=20 address assignment task really be treated independent from the routing task= ?=20 Or do we always have to bear in mind which routing protocol is used? > Unless of course we talk alternative or different Internet designs, or > micro-mobility, or MANETs. For all these there's a large body of > publications, Internet Drafts and patents. I'm not sure what you look > for exactly. I am talking about MANETs with Internet connectivity. Kind regards Volker B=F6hme _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www1.ietf.org/mailman/listinfo/autoconf 0 Oct 2007 06:53:12 -0400 Received: (qmail 4065 invoked from network); 30 Oct 2007 10:53:11 -0000 Received: from unknown (HELO 3-036.vpn.RWTH-Aachen.DE) (159037@[134.130.243.36]) (envelope-sender ) by smtprelay03.ispgateway.de (qmail-ldap-1.03) with SMTP; 30 Oct 2007 10:53:11 -0000 From: Volker =?iso-8859-1?q?B=F6hme?= To: Alexandru Petrescu Subject: Re: [Autoconf] Effect of IP assignment on routing Date: Tue, 30 Oct 2007 11:53:09 +0100 User-Agent: KMail/1.9.7 References: <200710251729.06666.mailinglisten@volker-boehme.de> <4721B5A8.9020104@gmail.com> In-Reply-To: <4721B5A8.9020104@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200710301153.09747.mailinglisten@volker-boehme.de> X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Cc: autoconf@ietf.org X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: autoconf-bounces@ietf.org Hi Alex, what you are talking about is not really what i had in mind. The scenario i= =20 was looking at it is as follows:=20 1. We have a MANET with Internet connectivity. 2. IP Address should be assigned to each node. 3. An ad-hoc routing protocol is used within the MANET. Now there are different possibilities which routing protocol can be used.=20 There are routing protocols which use flat routing (AODV,OLSR) and there ar= e=20 routing protocols which use hierarchical routing (ZRP, HARP). My question= =20 know is, if there are any studies about the effect of used autoconfiguratio= n=20 algorithm regarding to the used routing protocol. How does the=20 autoconfiguration algorithm effect the routing tabels? On Friday 26 October 2007 11:38:48 you wrote: > This is a bit normal. Normally, assigning an address to a node always > respects the pre-established addressing topology; routing is not > supposed to change upon address assignment. But the routing tables depend on how the address are assigned. So can the=20 address assignment task really be treated independent from the routing task= ?=20 Or do we always have to bear in mind which routing protocol is used? > Unless of course we talk alternative or different Internet designs, or > micro-mobility, or MANETs. For all these there's a large body of > publications, Internet Drafts and patents. I'm not sure what you look > for exactly. I am talking about MANETs with Internet connectivity. Kind regards Volker B=F6hme _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www1.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Wed Oct 31 10:59:32 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1InF2G-00086C-GY; Wed, 31 Oct 2007 10:59:12 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1InF2F-000854-48 for autoconf-confirm+ok@megatron.ietf.org; Wed, 31 Oct 2007 10:59:11 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1InF2E-00084q-76 for autoconf@ietf.org; Wed, 31 Oct 2007 10:59:10 -0400 Received: from mail119.messagelabs.com ([216.82.241.179]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1InF2C-0000ff-Lw for autoconf@ietf.org; Wed, 31 Oct 2007 10:59:09 -0400 X-VirusChecked: Checked X-Env-Sender: alexandru.petrescu@gmail.com X-Msg-Ref: server-10.tower-119.messagelabs.com!1193842747!31061152!1 X-StarScan-Version: 5.5.12.14.2; banners=.,-,- X-Originating-IP: [144.189.100.103] Received: (qmail 10938 invoked from network); 31 Oct 2007 14:59:07 -0000 Received: from motgate3.mot.com (HELO motgate3.mot.com) (144.189.100.103) by server-10.tower-119.messagelabs.com with SMTP; 31 Oct 2007 14:59:07 -0000 Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234]) by motgate3.mot.com (8.12.11/Motorola) with ESMTP id l9VEwv4e022654; Wed, 31 Oct 2007 07:59:01 -0700 (MST) Received: from az10vts01 (az10vts01.mot.com [10.64.251.242]) by az33exr04.mot.com (8.13.1/Vontu) with SMTP id l9VEwuUD016794; Wed, 31 Oct 2007 09:58:57 -0500 (CDT) Received: from [127.0.0.1] (zfr01-2117.crm.mot.com [10.161.201.117]) by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id l9VEwsYK016693; Wed, 31 Oct 2007 09:58:55 -0500 (CDT) Message-ID: <47289828.7070103@gmail.com> Date: Wed, 31 Oct 2007 15:58:48 +0100 From: Alexandru Petrescu User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: =?ISO-8859-1?Q?Volker_B=F6hme?= Subject: Re: [Autoconf] Effect of IP assignment on routing References: <200710251729.06666.mailinglisten@volker-boehme.de> <4721B5A8.9020104@gmail.com> <200710301153.09747.mailinglisten@volker-boehme.de> In-Reply-To: <200710301153.09747.mailinglisten@volker-boehme.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Antivirus: avast! (VPS 071031-0, 31/10/2007), Outbound message X-Antivirus-Status: Clean X-CFilter-Loop: Reflected X-Spam-Score: 0.0 (/) X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c Cc: autoconf@ietf.org X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: autoconf-bounces@ietf.org Volker Böhme wrote: > Hi Alex, > > what you are talking about is not really what i had in mind. The scenario i > was looking at it is as follows: > 1. We have a MANET with Internet connectivity. > 2. IP Address should be assigned to each node. > 3. An ad-hoc routing protocol is used within the MANET. > Now there are different possibilities which routing protocol can be used. > There are routing protocols which use flat routing (AODV,OLSR) and there are > routing protocols which use hierarchical routing (ZRP, HARP). My question > know is, if there are any studies about the effect of used autoconfiguration > algorithm regarding to the used routing protocol. How does the > autoconfiguration algorithm effect the routing tabels? (sorry, I don't know about studies). From my readings of MANET protocols they don't consider the address autoconfiguration algorithm when they consider routing, neither vice-versa. But that's just my limited reading. > On Friday 26 October 2007 11:38:48 you wrote: >> This is a bit normal. Normally, assigning an address to a node always >> respects the pre-established addressing topology; routing is not >> supposed to change upon address assignment. > > But the routing tables depend on how the address are assigned. So can the > address assignment task really be treated independent from the routing task? Normally yes. Normally a network planner first plans the addresses on the topology, which normally stays fixed. This address plan is reflected in DHCP and OSPF configuration files. These configuration files are fixed. > Or do we always have to bear in mind which routing protocol is used? I think in AUTOCONF and MANET one would like to have the address assignment to influence routing, and vice-versa. But the requirement sets can be so different, here's but an example: -mobiles can change their addresses but routers no. -routes must stay fixed but addresses can change. -etc. >> Unless of course we talk alternative or different Internet designs, or >> micro-mobility, or MANETs. For all these there's a large body of >> publications, Internet Drafts and patents. I'm not sure what you look >> for exactly. > > I am talking about MANETs with Internet connectivity. Right... a MANET connecting to the Internet may obtain its addresses from the fixed infrastructure with DHCP-PD, which will probably add routes upon each access. It could also try to continue using same set of addresses at each access, thus forcing the access network to route its set of addresses (not use DHCP-PD). (Sorry, I don't know about publications, but why do you ask?) Alex ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www1.ietf.org/mailman/listinfo/autoconf