From autoconf-bounces@ietf.org Sun Sep 02 10:54:11 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IRqq3-0003Q9-2n; Sun, 02 Sep 2007 10:54:11 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1IRqq2-0003Q0-Di for autoconf-confirm+ok@megatron.ietf.org; Sun, 02 Sep 2007 10:54:10 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IRqpy-0003Pn-7t; Sun, 02 Sep 2007 10:54:06 -0400 Received: from [202.99.23.227] (helo=people.com.cn) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IRqpx-0005cZ-9x; Sun, 02 Sep 2007 10:54:06 -0400 Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jm1146db2537; Sun, 02 Sep 2007 23:06:17 +0800 Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jmad46d5f044; Thr, 30 Aug 2007 05:05:50 +0800 Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC 2.9.5.8) with SMTP id AISP action; Thr, 30 Aug 2007 05:05:50 +0800 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQUDw-00026A-LR; Wed, 29 Aug 2007 16:33:12 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQTwr-0000Ir-5t; Wed, 29 Aug 2007 16:15:35 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQTwq-0000IQ-NS; Wed, 29 Aug 2007 16:15:33 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 82DC12AC79; Wed, 29 Aug 2007 20:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IQTwM-0004CT-72; Wed, 29 Aug 2007 16: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: Wed, 29 Aug 2007 16:15:02 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8 X-BeenThere: i-d-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list X-AIMC-AUTH: (null) X-AIMC-MAILFROM: i-d-announce-bounces@ietf.org X-AIMC-AUTH: (null) X-AIMC-MAILFROM: Internet-Drafts@ietf.org X-Auto-Forward: jaglee@people.com.cn jag@kw.com.cn X-Spam-Score: 2.8 (++) X-Scan-Signature: 386e0819b1192672467565a524848168 Cc: autoconf@ietf.org Subject: [Autoconf] I-D ACTION:draft-ietf-autoconf-manetarch-05.txt X-BeenThere: autoconf@ietf.org Reply-To: internet-drafts@ietf.org 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-05.txt Pages : 22 Date : 2007-8-29 This document discusses Mobile Ad hoc NETworks (MANETs). It introduces basic MANET terms, characteristics, and challenges and defines fundamental MANET entities and architectural concepts. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-autoconf-manetarch-05.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-05.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-05.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-8-29151850.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-autoconf-manetarch-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-autoconf-manetarch-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-8-29151850.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce --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 Sep 03 10:27:59 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ISCuE-0001x9-Vc; Mon, 03 Sep 2007 10:27:58 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1ISCuD-0001wI-3F for autoconf-confirm+ok@megatron.ietf.org; Mon, 03 Sep 2007 10:27:57 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ISCuC-0001v4-Np for autoconf@ietf.org; Mon, 03 Sep 2007 10:27:56 -0400 Received: from mailout1.samsung.com ([203.254.224.24]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ISCuA-0005J0-VV for autoconf@ietf.org; Mon, 03 Sep 2007 10:27:56 -0400 Received: from epmmp1 (mailout1.samsung.com [203.254.224.24]) by mailout1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0JNS00FXZQUHGM@mailout1.samsung.com> for autoconf@ietf.org; Mon, 03 Sep 2007 23:27:53 +0900 (KST) Received: from Shubhranshu ([107.108.4.124]) by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTPA id <0JNS00ALFQUENR@mmp1.samsung.com> for autoconf@ietf.org; Mon, 03 Sep 2007 23:27:53 +0900 (KST) Date: Mon, 03 Sep 2007 19:58:21 +0530 From: Shubhranshu To: autoconf@ietf.org Message-id: <028e01c7ee36$af638c90$7c046c6b@sisodomain.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-Mailer: Microsoft Outlook Express 6.00.2900.3028 X-Priority: 3 X-MSMail-priority: Normal X-Spam-Score: -4.0 (----) X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3 Cc: Thomas Clausen , macker@itd.nrl.navy.mil Subject: [Autoconf] WG Last Call: Draft-ietf-autoconf-manetarch-05.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: , Content-Type: multipart/mixed; boundary="===============0436261999==" Errors-To: autoconf-bounces@ietf.org This is a multi-part message in MIME format. --===============0436261999== Content-type: multipart/alternative; boundary="Boundary_(ID_yK0q00nRKizTP6F4i6JkvQ)" This is a multi-part message in MIME format. --Boundary_(ID_yK0q00nRKizTP6F4i6JkvQ) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Hi All, This is a Working Group Last Call (WGLC) for comments on "Mobile Ad Hoc Network Architecture", Draft-ietf-autoconf-manetarch-05.txt. The document is available at http://tools.ietf.org/id/draft-ietf-autoconf-manetarch-05.txt . The document is intended for publication as an Informational RFC. Please review the document and send your comments to the mailing list. This WGLC will end on Monday, September, 24th. Thanks, Shubhranshu Autoconf WG Co-Chair --Boundary_(ID_yK0q00nRKizTP6F4i6JkvQ) Content-type: text/html; charset=iso-8859-1 Content-transfer-encoding: 7BIT
Hi All,
 
This is a Working Group Last Call (WGLC) for comments on "Mobile
Ad Hoc Network Architecture", Draft-ietf-autoconf-manetarch-05.txt. The
 
The document is intended for publication as an Informational RFC.
 
Please review the document and send your comments to the mailing list.
 
This WGLC will end on Monday, September, 24th.
 
Thanks,
Shubhranshu
Autoconf WG Co-Chair
--Boundary_(ID_yK0q00nRKizTP6F4i6JkvQ)-- --===============0436261999== 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 --===============0436261999==-- From autoconf-bounces@ietf.org Tue Sep 04 23:20: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 1ISlRc-0002J8-Rp; Tue, 04 Sep 2007 23:20:44 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1ISlRa-0002DD-LZ for autoconf-confirm+ok@megatron.ietf.org; Tue, 04 Sep 2007 23:20:42 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ISlRa-0002D5-By for autoconf@ietf.org; Tue, 04 Sep 2007 23:20:42 -0400 Received: from rv-out-0910.google.com ([209.85.198.184]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ISlRZ-0004wj-5U for autoconf@ietf.org; Tue, 04 Sep 2007 23:20:42 -0400 Received: by rv-out-0910.google.com with SMTP id l15so1273817rvb for ; Tue, 04 Sep 2007 20:20:40 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=KZrSZkiZcCshNm3Nb8l20qCDGMs9tLGzmxtOBq8vCKNC251kPNh0vW05ThvaJORsuGpDZLe2FHvdtJ8Y4OjvNBdrLH105nkPifiU3LnDZ6Oje1awaDsN14VFThGXw1yWOb1cAXvjxixACs/vCKONQra7Olb8ebFHZEhmOgJb2LU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=dZeZZ/t2FztO6VDgD7gRxkc51V80upjMuEtXMgm2YNUjP7qYiXRSIlhetfyYIEKhcorUSZQF5Hs/UR+9esFUpT8MuLDY+KfEkGIeZsikc88V0KYEAi1fr1pbRyO3TelClylcdVl44UfP2Wp5/lVCKh37p16zG39FEYK/q8ZAFBQ= Received: by 10.142.131.18 with SMTP id e18mr339270wfd.1188962440350; Tue, 04 Sep 2007 20:20:40 -0700 (PDT) Received: by 10.143.35.15 with HTTP; Tue, 4 Sep 2007 20:20:40 -0700 (PDT) Message-ID: <422902b70709042020x79bac3c8o29b1280d904ff7b4@mail.gmail.com> Date: Wed, 5 Sep 2007 08:50:40 +0530 From: "Siddharth Malhotra" To: autoconf@ietf.org Subject: RE: [Autoconf] WG Last Call: Draft-ietf-autoconf-manetarch-05.txt MIME-Version: 1.0 X-Spam-Score: 0.0 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 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="===============0968292583==" Errors-To: autoconf-bounces@ietf.org --===============0968292583== Content-Type: multipart/alternative; boundary="----=_Part_51624_324290.1188962440314" ------=_Part_51624_324290.1188962440314 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello Thomas, I would like to point out in the security considerations section that it has just been mentioned about the external intrusion whereas nothing has been mention about internal intrusion and selfish behavior of the routers like they stop forwarding packets of all the nodes or even they can show malicious behavior towards certain or a single node. Thanks Siddharth Malhotra ------=_Part_51624_324290.1188962440314 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello Thomas,

I would like to point out in the security considerations section that it has just been mentioned about the external intrusion whereas nothing has been mention about internal intrusion and selfish behavior of the routers like they stop forwarding packets of all the nodes or even they can show malicious behavior towards certain or a single node.

Thanks

Siddharth Malhotra ------=_Part_51624_324290.1188962440314-- --===============0968292583== 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 --===============0968292583==-- From autoconf-bounces@ietf.org Wed Sep 05 15:15: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 1IT0Lp-0005Es-As; Wed, 05 Sep 2007 15:15:45 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1IT0Ld-0004op-Gr for autoconf-confirm+ok@megatron.ietf.org; Wed, 05 Sep 2007 15:15:33 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IT0Lc-0004oX-Vi; Wed, 05 Sep 2007 15:15:33 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IT0Lc-00060B-6f; Wed, 05 Sep 2007 15:15:32 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 1AF322AC63; Wed, 5 Sep 2007 19:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IT0L7-0003Ol-Rx; Wed, 05 Sep 2007 15:15:01 -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: Wed, 05 Sep 2007 15:15:01 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Cc: autoconf@ietf.org Subject: [Autoconf] I-D ACTION:draft-ietf-autoconf-statement-01.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 : Address Autoconfiguration for MANET: Terminology and Problem Statement Author(s) : E. Baccelli, et al. Filename : draft-ietf-autoconf-statement-01.txt Pages : 18 Date : 2007-9-5 Traditional dynamic IPv6 address assignment solutions are not adapted to mobile ad hoc networks. This document elaborates on this problem, states the need for new solutions, and requirements to these solutions. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-autoconf-statement-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 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-statement-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-ietf-autoconf-statement-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-Type: text/plain Content-ID: <2007-9-5144550.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-autoconf-statement-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-autoconf-statement-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-9-5144550.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 Thu Sep 06 09:11: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 1ITH8S-0004PG-Fe; Thu, 06 Sep 2007 09:11:04 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1ITH8R-0004PA-2C for autoconf-confirm+ok@megatron.ietf.org; Thu, 06 Sep 2007 09:11:03 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ITH8Q-0004P2-Nd for autoconf@ietf.org; Thu, 06 Sep 2007 09:11:02 -0400 Received: from mailout3.samsung.com ([203.254.224.33]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ITH8P-0001GJ-V8 for autoconf@ietf.org; Thu, 06 Sep 2007 09:11:02 -0400 Received: from epmmp1 (mailout3.samsung.com [203.254.224.33]) by mailout3.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0JNY0006F7AAKI@mailout3.samsung.com> for autoconf@ietf.org; Thu, 06 Sep 2007 22:10:58 +0900 (KST) Received: from Shubhranshu ([107.108.4.124]) by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTPA id <0JNY00GXQ7AAM0@mmp1.samsung.com> for autoconf@ietf.org; Thu, 06 Sep 2007 22:10:59 +0900 (KST) Date: Thu, 06 Sep 2007 18:41:31 +0530 From: Shubhranshu Subject: Re: [Autoconf] WG Last Call: Draft-ietf-autoconf-manetarch-05.txt To: Siddharth Malhotra Message-id: <020b01c7f087$72877680$7c046c6b@sisodomain.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-Mailer: Microsoft Outlook Express 6.00.2900.3028 X-Priority: 3 X-MSMail-priority: Normal X-Spam-Score: 2.2 (++) X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 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="===============1873156538==" Errors-To: autoconf-bounces@ietf.org This is a multi-part message in MIME format. --===============1873156538== Content-type: multipart/alternative; boundary="Boundary_(ID_lIGOxFOMKp+27p7qKxht9w)" This is a multi-part message in MIME format. --Boundary_(ID_lIGOxFOMKp+27p7qKxht9w) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT > ----- Original Message ----- > From: Siddharth Malhotra > To: autoconf@ietf.org > I would like to point out in the security considerations section that it has > just been mentioned about the external intrusion whereas nothing has been > mention about internal intrusion and selfish behavior of the routers like > they stop forwarding packets of all the nodes > Could you elaborate further? Isn't it just a node specific routing behavior, where it decides to behave as a leaf node. - Shubhranshu > or even they can show malicious behavior towards certain or a single node. > > Thanks > Siddharth Malhotra --Boundary_(ID_lIGOxFOMKp+27p7qKxht9w) Content-type: text/html; charset=iso-8859-1 Content-transfer-encoding: 7BIT
 
> ----- Original Message -----
> From: Siddharth Malhotra
> To: autoconf@ietf.org 
> I would like to point out in the security considerations section that it has
> just been mentioned about the external intrusion whereas nothing has been
> mention about internal intrusion and selfish behavior of the routers like
> they stop forwarding packets of all the nodes
> 
 
Could you elaborate further? Isn't it just a node specific routing behavior, where
it decides to behave as a leaf node.
 
- Shubhranshu 
 
> or even they can show malicious behavior towards certain or a single node.
>
> Thanks
> Siddharth Malhotra

--Boundary_(ID_lIGOxFOMKp+27p7qKxht9w)-- --===============1873156538== 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 --===============1873156538==-- From autoconf-bounces@ietf.org Mon Sep 10 10:05:20 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IUjtA-0005b2-Aa; Mon, 10 Sep 2007 10:05:20 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1IUjt9-0005Wp-9U for autoconf-confirm+ok@megatron.ietf.org; Mon, 10 Sep 2007 10:05:19 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IUjt7-0005UI-Gz for autoconf@ietf.org; Mon, 10 Sep 2007 10:05:17 -0400 Received: from mailout2.samsung.com ([203.254.224.25]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IUjt5-0006Vl-Ok for autoconf@ietf.org; Mon, 10 Sep 2007 10:05:17 -0400 Received: from epmmp1 (mailout2.samsung.com [203.254.224.25]) by mailout2.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0JO5006SWOEEA8@mailout2.samsung.com> for autoconf@ietf.org; Mon, 10 Sep 2007 23:03:50 +0900 (KST) Received: from Shubhranshu ([107.108.4.124]) by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTPA id <0JO5008VKOECW1@mmp1.samsung.com> for autoconf@ietf.org; Mon, 10 Sep 2007 23:03:50 +0900 (KST) Date: Mon, 10 Sep 2007 19:34:30 +0530 From: Shubhranshu To: autoconf@ietf.org Message-id: <021c01c7f3b3$82d6cfc0$7c046c6b@sisodomain.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-Mailer: Microsoft Outlook Express 6.00.2900.3028 Content-type: text/plain; reply-type=response; charset=iso-8859-15; format=flowed Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal X-Spam-Score: -4.0 (----) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Subject: [Autoconf] Fw: Nomcom 2007-8: Nominations Close on Sep 10, 2007 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 Please find below the Nomcom Chairs' mail requesting feedback and nominations. - Shubhranshu ----- Original Message ----- From: "Lakshminath Dondeti" Subject: Nomcom 2007-8: Nominations Close on Sep 10, 2007 > All, > > Here is the link to nominate: > https://tools.ietf.org/group/nomcom/07/nominate > > You may also send nominations or comments via email to nomcom07@ietf.org > or ldondeti@qualcomm.com. > > We have received very few nominations (1, 2, 2, 2, 3, 4, 8, 8, 19) and > even fewer accepted (1-2 people in each area, IAB acceptances is 4 at > last count). > > I request the community to provide feedback on the incumbents (send > email or send notes via the web page). > > 1) If you think that the incumbent is doing a good job > a) provide feedback AND > b) nominate similar people just in case there is strong negative > feedback on the incumbent > > 2) If you think the incumbent can do somethings better > a) provide feedback AND > b) nominate someone who you think might do better > > Candidates, if time commitment is the only issue, please indicate that > to the nomcom and accept the nominations. > > thanks, > Lakshminath > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf-announce > > _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www1.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Thu Sep 20 20:22: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 1IYWHV-00062g-OF; Thu, 20 Sep 2007 20:22:05 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1IYWHU-00062V-HV for autoconf-confirm+ok@megatron.ietf.org; Thu, 20 Sep 2007 20:22:04 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IYWHU-0005zJ-4p for autoconf@ietf.org; Thu, 20 Sep 2007 20:22:04 -0400 Received: from py-out-1112.google.com ([64.233.166.181]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IYWHK-0006IV-0g for autoconf@ietf.org; Thu, 20 Sep 2007 20:22:00 -0400 Received: by py-out-1112.google.com with SMTP id d32so2372301pye for ; Thu, 20 Sep 2007 17:21:14 -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:mime-version:content-type:content-transfer-encoding:content-disposition; bh=ZLatWlT1F/12uh0QCw+jFhDFQJuDf0pRdiI9TWdjhXs=; b=Ht5arecTwNmXJ7NfPaXXLeM5DdT5STibMygs6swSzP6Umwe4jwl5I7m4AFC/RX+2tlf5vB0MJk/3G+skgWEbeKkF3b0cQE5xeUWZdY1ktpPqUj20I9IV7NLNz3ayyttExKK06HMzpqn8R1IG2jpjgRLp+Z19ft4oCWAtb9tqIAE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=XOBv0qzO2kCVIW3RPhPVnHb22rjLSYDq1+TJymzhL+OEdatgolrLe/ZPhskn3QyPsWBu6xczgRn45YUChDkeMg5BWkoyKcUmkp0Mj2WmcM+srYmlNP+EapnzZXuq2435MDRpTQepr3JY2nC98DT1qPOAPLZdSgCZiAG3QX4ETJk= Received: by 10.65.61.5 with SMTP id o5mr5378284qbk.1190334072917; Thu, 20 Sep 2007 17:21:12 -0700 (PDT) Received: by 10.65.98.17 with HTTP; Thu, 20 Sep 2007 17:21:12 -0700 (PDT) Message-ID: Date: Fri, 21 Sep 2007 05:51:12 +0530 From: Shubhranshu To: autoconf@ietf.org Subject: Fw: [Autoconf] WG Last Call: Draft-ietf-autoconf-manetarch-05.txt MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f 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 A reminder mail: I would like to encourage all to review this I-D by this Monday, the WGLC cut-off date. If you review this ID and find any specific concerns or comments then send them to the list. Also, let the list or the chairs know if you find it fine to move the ID forward. Thanks, Shubhranshu ----- Original Message ----- From: Shubhranshu To: autoconf@ietf.org Cc: Thomas Clausen ; macker@itd.nrl.navy.mil Sent: Monday, September 03, 2007 7:58 PM Subject: [Autoconf] WG Last Call: Draft-ietf-autoconf-manetarch-05.txt Hi All, This is a Working Group Last Call (WGLC) for comments on "Mobile Ad Hoc Network Architecture", Draft-ietf-autoconf-manetarch-05.txt. The document is available at http://tools.ietf.org/id/draft-ietf-autoconf-manetarch-05.txt . The document is intended for publication as an Informational RFC. Please review the document and send your comments to the mailing list. This WGLC will end on Monday, September, 24th. Thanks, Shubhranshu Autoconf WG Co-Chair _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www1.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Fri Sep 21 00:45:57 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IYaOY-0006Vm-8o; Fri, 21 Sep 2007 00:45:38 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1IYaOX-0006Vf-DC for autoconf-confirm+ok@megatron.ietf.org; Fri, 21 Sep 2007 00:45:37 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IYaOX-0006VW-3O for autoconf@ietf.org; Fri, 21 Sep 2007 00:45:37 -0400 Received: from nf-out-0910.google.com ([64.233.182.187]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IYaOQ-0003pX-Tv for autoconf@ietf.org; Fri, 21 Sep 2007 00:45:37 -0400 Received: by nf-out-0910.google.com with SMTP id d21so605725nfb for ; Thu, 20 Sep 2007 21:45:06 -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:content-transfer-encoding:content-disposition; bh=MmJyhCmCPC+Bn6BS/NiSPefFFgYraek8FjrDk4yhUPo=; b=Rb13nxydTRTKklD7EDKxjYVqFPIM3hjMiv7epSlwLh5OS/q7tpU9dYvC7WwCfQanC2kNmQIliPaTFII91Sc9ysHmfWQ+TKgso5km6rvQHDlwGydkgDuZ2u5Mgt68Vcj7G9TeZW4S/FYc/oE4/zz1Ov9+HhNNG6PVbwzSCx1TloQ= 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:content-transfer-encoding:content-disposition; b=Lj2Hd2MzxMFJ7A4LS5w0bq+DHlQ9bQhIjrsqx1VV5ISiKx9IZCvEGWekQUBWaWF/J4D91LACRXpB5P/qAgpTRjJjjG7vOoPGFXHPx8sBcndUZHigg1+uopo+BGj9sC7TjwpwZSIe2Q2XftF6crcUdoxckY3KNP7wh9mUtkgsEAg= Received: by 10.78.97.7 with SMTP id u7mr1733408hub.1190349905802; Thu, 20 Sep 2007 21:45:05 -0700 (PDT) Received: by 10.78.53.8 with HTTP; Thu, 20 Sep 2007 21:45:05 -0700 (PDT) Message-ID: <374005f30709202145y51bd5d8atb099830744e91f74@mail.gmail.com> Date: Fri, 21 Sep 2007 10:15:05 +0530 From: "Ian Chakeres" To: autoconf@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Cc: "Singh Shubhranshu \(home\)" , "Thomas Heide Clausen \(work\)" Subject: [Autoconf] MANET-ARCH-05 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 happy to report that we've received several excellent comments regarding MANET-ARCH during WGLC. I'd also like to write about a few of the changes made in the arch-05 revision. Several of the changes were made based on Fred Templin's arch-04 comments. I would like to point out that Fred's suggestion to change usage of term interface to link in many places was not made. The use of interface, link, subnet, and several other terms have been highly debated and the current usage has been agreed upon by people from different areas/backgrounds. That said, the new revision of the document will address the fine comments we've received during WGLC. If you have any additional comments, please send them ASAP. Ian Chakeres _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www1.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Fri Sep 21 03:14: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 1IYciT-0005wr-VW; Fri, 21 Sep 2007 03:14:21 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1IYciS-0005wh-Ph for autoconf-confirm+ok@megatron.ietf.org; Fri, 21 Sep 2007 03:14:20 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IYciO-0005nw-Ef for autoconf@ietf.org; Fri, 21 Sep 2007 03:14:16 -0400 Received: from hpsmtp-eml15.kpnxchange.com ([213.75.38.115]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IYciJ-0002NI-Cn for autoconf@ietf.org; Fri, 21 Sep 2007 03:14:11 -0400 Received: from hpsmtp-eml09.kpnxchange.com ([213.75.38.109]) by hpsmtp-eml15.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 21 Sep 2007 09:14:10 +0200 Received: from M90Teco ([86.83.9.22]) by hpsmtp-eml09.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 21 Sep 2007 09:14:09 +0200 From: "Teco Boot" To: "'Ian Chakeres'" References: <374005f30709202145y51bd5d8atb099830744e91f74@mail.gmail.com> In-Reply-To: <374005f30709202145y51bd5d8atb099830744e91f74@mail.gmail.com> Subject: RE: [Autoconf] MANET-ARCH-05 Date: Fri, 21 Sep 2007 09:14:08 +0200 Message-ID: <001a01c7fc1f$0066a0a0$0133e1e0$@nl> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acf8CuxwPMuIpYkDQDyLF3gP//fsYwACyW5A Content-Language: nl X-OriginalArrivalTime: 21 Sep 2007 07:14:09.0708 (UTC) FILETIME=[012A3EC0:01C7FC1F] X-Spam-Score: 0.0 (/) X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db 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 Ian, Small remark on some diagrams. Loopback is "internal" interface, but drawn outside the MNR block in section 2.2 In section 5.1, the loopback is drawn inside the MNR block. Note that all MNR interfaces have an IP address assigned, so the difference is that on loopback interfaces, there are no external nodes connected. In the diagram in 5.1, the MNR has itself also a P:2:: address. Below a proposal for the diagram. MANET <~~~~~~+~~~~~~> Delegated Interface | Prefix | ========= ''''''''''''''''''|'''''''''''' <=== P:: = ' | ' ========= ' MANET Router ' ' : : ' ' P:2::mnr=>: :<=P:1::mnr ' Assigned ' : : ' Prefixes ' : +--------+ ' ========= ' : |Loopback| ' <=== P:1:: = ' : +--------+ ' ========= '''''''''''':'''''''''''''''''' : ========= ============ +....:..+.....+ <====== P:2:: = = : = : : ========= = : = :<=P:2::1 :<=P:2::k =Classic IP= +-+-+ +-+-+ =Interfaces= | N | * * * | N | ============ +---+ +---+ I doubt depicting the MANET Interface address. It could be added, as an introduction to the next section 5.2. It makes the MANET Router and Prefixes diagram complete. MANET <~~~~~~+~~~~~~> Delegated Interface | Prefix | ========= ''''''''''''''''''|'''''''''''' <=== P:: = ' Unique Prefix=>| ' ========= ' | ' ' MANET Router ' ' : : ' ' P:2::mnr=>: :<=P:1::mnr ' Assigned ' : : ' Prefixes ' : +--------+ ' ========= ' : |Loopback| ' <=== P:1:: = ' : +--------+ ' ========= '''''''''''':'''''''''''''''''' : ========= ============ +....:..+.....+ <====== P:2:: = = : = : : ========= = : = :<=P:2::1 :<=P:2::k =Classic IP= +-+-+ +-+-+ =Interfaces= | N | * * * | N | ============ +---+ +---+ Teco. > -----Oorspronkelijk bericht----- > Van: Ian Chakeres [mailto:ian.chakeres@gmail.com] > Verzonden: vrijdag 21 september 2007 6:45 > Aan: autoconf@ietf.org > CC: Singh Shubhranshu (home); Thomas Heide Clausen (work) > Onderwerp: [Autoconf] MANET-ARCH-05 > > I'm happy to report that we've received several excellent comments > regarding MANET-ARCH during WGLC. > > I'd also like to write about a few of the changes made in the arch-05 > revision. Several of the changes were made based on Fred Templin's > arch-04 comments. I would like to point out that Fred's suggestion to > change usage of term interface to link in many places was not made. > The use of interface, link, subnet, and several other terms have been > highly debated and the current usage has been agreed upon by people > from different areas/backgrounds. > > That said, the new revision of the document will address the fine > comments we've received during WGLC. > > If you have any additional comments, please send them ASAP. > Ian Chakeres > > > _______________________________________________ > 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 Fri Sep 21 11:57:57 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IYkt1-0005Tw-Q3; Fri, 21 Sep 2007 11:57:47 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1IYkt0-0005Sg-Io for autoconf-confirm+ok@megatron.ietf.org; Fri, 21 Sep 2007 11:57:46 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IYkt0-0005SY-2g for autoconf@ietf.org; Fri, 21 Sep 2007 11:57:46 -0400 Received: from blv-smtpout-01.boeing.com ([130.76.32.69]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IYksz-00085w-7q for autoconf@ietf.org; Fri, 21 Sep 2007 11:57:45 -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 l8LFvbvr011101 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 21 Sep 2007 08:57:42 -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 l8LFvaxw023963; Fri, 21 Sep 2007 10:57:37 -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 l8LFvY2d023864; Fri, 21 Sep 2007 10:57:34 -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, 21 Sep 2007 08:57:33 -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] MANET-ARCH-05 Date: Fri, 21 Sep 2007 08:57:28 -0700 Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029EDA8F@XCH-NW-7V2.nw.nos.boeing.com> In-Reply-To: <001a01c7fc1f$0066a0a0$0133e1e0$@nl> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Autoconf] MANET-ARCH-05 Thread-Index: Acf8CuxwPMuIpYkDQDyLF3gP//fsYwACyW5AABOdR+A= References: <374005f30709202145y51bd5d8atb099830744e91f74@mail.gmail.com> <001a01c7fc1f$0066a0a0$0133e1e0$@nl> From: "Templin, Fred L" To: "Teco Boot" , "Ian Chakeres" X-OriginalArrivalTime: 21 Sep 2007 15:57:33.0064 (UTC) FILETIME=[1F061880:01C7FC68] X-Spam-Score: 0.0 (/) X-Scan-Signature: c54bc2f42d02429833c0ca4b8725abd7 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 Teco,=20 > -----Original Message----- > From: Teco Boot [mailto:teco@inf-net.nl]=20 > Sent: Friday, September 21, 2007 12:14 AM > To: 'Ian Chakeres' > Cc: autoconf@ietf.org > Subject: RE: [Autoconf] MANET-ARCH-05 >=20 > Hi Ian, >=20 > Small remark on some diagrams. > Loopback is "internal" interface, but drawn outside the MNR block in section > 2.2 > In section 5.1, the loopback is drawn inside the MNR block. > Note that all MNR interfaces have an IP address assigned, so the difference > is that on loopback interfaces, there are no external nodes connected. > In the diagram in 5.1, the MNR has itself also a P:2:: address. Below a > proposal for the diagram.=20 >=20 >=20 > MANET <~~~~~~+~~~~~~> Delegated > Interface | Prefix > | = =3D=3D=3D=3D=3D=3D=3D=3D=3D > ''''''''''''''''''|'''''''''''' <=3D=3D=3D P:: =3D =20 > ' | ' = =3D=3D=3D=3D=3D=3D=3D=3D=3D > ' MANET Router ' =20 > ' : : ' > ' P:2::mnr=3D>: :<=3DP:1::mnr ' Assigned > ' : : ' Prefixes > ' : +--------+ ' = =3D=3D=3D=3D=3D=3D=3D=3D=3D > ' : |Loopback| ' <=3D=3D=3D P:1:: =3D > ' : +--------+ ' = =3D=3D=3D=3D=3D=3D=3D=3D=3D > '''''''''''':'''''''''''''''''' =20 > : = =3D=3D=3D=3D=3D=3D=3D=3D=3D > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D +....:..+.....+ = <=3D=3D=3D=3D=3D=3D P:2:: =3D > =3D : =3D : : = =3D=3D=3D=3D=3D=3D=3D=3D=3D > =3D : =3D :<=3DP:2::1 :<=3DP:2::k=20 > =3DClassic IP=3D +-+-+ +-+-+ > =3DInterfaces=3D | N | * * * | N | > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D +---+ +---+ Two things here. First, it need not be a singluar loopback interface. It could be many loopback interfaces and/or other internal virtual interfaces, with many internal virtual networks and virtual hosts attached. Second, MNR's do not assign addresses derived from their delegated prefixes to interfaces that connect directly to the Internet/provider/visited network/etc, i.e., in the case of a MNR that is also a BR. That is why IMHO it is necessary to distinguish egress interfaces (those that connect the MNR to the Internet/provider/visited network/etc) from ingress interfaces (those via which the MNR connects mobile networks). Fred fred.l.templin@boeing.com=20 > I doubt depicting the MANET Interface address. It could be added, as an > introduction to the next section 5.2. It makes the MANET Router and Prefixes > diagram complete. >=20 >=20 > MANET <~~~~~~+~~~~~~> Delegated > Interface | Prefix > | = =3D=3D=3D=3D=3D=3D=3D=3D=3D > ''''''''''''''''''|'''''''''''' <=3D=3D=3D P:: =3D =20 > ' Unique Prefix=3D>| ' = =3D=3D=3D=3D=3D=3D=3D=3D=3D > ' | ' > ' MANET Router ' =20 > ' : : ' > ' P:2::mnr=3D>: :<=3DP:1::mnr ' Assigned > ' : : ' Prefixes > ' : +--------+ ' = =3D=3D=3D=3D=3D=3D=3D=3D=3D > ' : |Loopback| ' <=3D=3D=3D P:1:: =3D > ' : +--------+ ' = =3D=3D=3D=3D=3D=3D=3D=3D=3D > '''''''''''':'''''''''''''''''' =20 > : = =3D=3D=3D=3D=3D=3D=3D=3D=3D > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D +....:..+.....+ = <=3D=3D=3D=3D=3D=3D P:2:: =3D > =3D : =3D : : = =3D=3D=3D=3D=3D=3D=3D=3D=3D > =3D : =3D :<=3DP:2::1 :<=3DP:2::k=20 > =3DClassic IP=3D +-+-+ +-+-+ > =3DInterfaces=3D | N | * * * | N | > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D +---+ +---+ >=20 >=20 > Teco. >=20 >=20 >=20 >=20 > > -----Oorspronkelijk bericht----- > > Van: Ian Chakeres [mailto:ian.chakeres@gmail.com] > > Verzonden: vrijdag 21 september 2007 6:45 > > Aan: autoconf@ietf.org > > CC: Singh Shubhranshu (home); Thomas Heide Clausen (work) > > Onderwerp: [Autoconf] MANET-ARCH-05 > >=20 > > I'm happy to report that we've received several excellent comments > > regarding MANET-ARCH during WGLC. > >=20 > > I'd also like to write about a few of the changes made in=20 > the arch-05 > > revision. Several of the changes were made based on Fred Templin's > > arch-04 comments. I would like to point out that Fred's=20 > suggestion to > > change usage of term interface to link in many places was not made. > > The use of interface, link, subnet, and several other terms=20 > have been > > highly debated and the current usage has been agreed upon by people > > from different areas/backgrounds. > >=20 > > That said, the new revision of the document will address the fine > > comments we've received during WGLC. > >=20 > > If you have any additional comments, please send them ASAP. > > Ian Chakeres > >=20 > >=20 > > _______________________________________________ > > Autoconf mailing list > > Autoconf@ietf.org > > https://www1.ietf.org/mailman/listinfo/autoconf >=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 Fri Sep 21 17:22: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 1IYpx5-0008Uf-1k; Fri, 21 Sep 2007 17:22:19 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1IYpx4-0008TY-88 for autoconf-confirm+ok@megatron.ietf.org; Fri, 21 Sep 2007 17:22:18 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IYpx3-00084L-O2 for autoconf@ietf.org; Fri, 21 Sep 2007 17:22:17 -0400 Received: from e4.ny.us.ibm.com ([32.97.182.144]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IYpwC-0002vy-1t for autoconf@ietf.org; Fri, 21 Sep 2007 17:21:24 -0400 Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e4.ny.us.ibm.com (8.13.8/8.13.8) with ESMTP id l8LLLNUt029886 for ; Fri, 21 Sep 2007 17:21:23 -0400 Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v8.5) with ESMTP id l8LLLNlo693284 for ; Fri, 21 Sep 2007 17:21:23 -0400 Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l8LLLN5a012354 for ; Fri, 21 Sep 2007 17:21:23 -0400 Received: from cichlid.raleigh.ibm.com (wecm-9-67-143-235.wecm.ibm.com [9.67.143.235]) by d01av03.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id l8LLLKAh012168 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 21 Sep 2007 17:21:22 -0400 Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.1/8.12.5) with ESMTP id l8LLLJlJ015801 for ; Fri, 21 Sep 2007 17:21:19 -0400 Message-Id: <200709212121.l8LLLJlJ015801@cichlid.raleigh.ibm.com> To: autoconf@ietf.org Subject: [Autoconf] MANET-ARCH-05 Date: Fri, 21 Sep 2007 17:21:19 -0400 From: Thomas Narten X-Spam-Score: 0.0 (/) X-Scan-Signature: 93df555cbdbcdae9621e5b95d44b301e 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 Ian Chakeres writes: > I'm happy to report that we've received several excellent comments > regarding MANET-ARCH during WGLC. > > I'd also like to write about a few of the changes made in the arch-05 > revision. Several of the changes were made based on Fred Templin's > arch-04 comments. I would like to point out that Fred's suggestion to > change usage of term interface to link in many places was not made. I just read the draft and I have great difficulty with the "interface" terminology. In my view (from a non-manet background), you are redefining a term that is widely used elsewhere and I find that very confusing. I think you should use something else. I too was thinking something with the word "link" in it (e.g., "manet link") would be better. Interfaces are a software abstraction, and are generally used to refer to, well, interfaces to physical (or virtual) networks (or links). This document uses the term to describe what in my view are link properties - characteristics of the MANET technology (e.g., non-asymetric reachability). That is a characteristic of the technology. > The use of interface, link, subnet, and several other terms have been > highly debated and the current usage has been agreed upon by people > from different areas/backgrounds. Not by me. > That said, the new revision of the document will address the fine > comments we've received during WGLC. > > If you have any additional comments, please send them ASAP. Can you say something about what changes are upcoming? In general, I find the document is still too fuzzy, especially with respect to when it is talking about "manet technology" in an abstract sense (like what its characteristics are) and when it is talking about manet in an IP environment (i.e, when unstated assumptions are made about what address nodes have, what prefixes mean, etc.) Some random specifics: Full-Broadcast Interface (FBI) A broadcast interface known to have both transitive and bidirectional communication, i.e. it does not exhibit asymmetric reachability. Nodes which are connected to the same link via Full-Broadcast Interfaces can all send and receive IP packets directly to each other -- all nodes are thus bi-directional neighbors. Ethernet interfaces connected via a single Ethernet segment is an example of a FBI. Hmm. How does "IP packets" fit into the above definition? Do all FBIs have an IP address associated with them? and or an IP prefix? isn't the bi-directional nature a property that has nothing to do with IP? Border Router (BR) a router that participates in multiple routing regions, and often multiple routing protocols. A BR defines the border between its multiple routing regions. A BR is responsible for presenting a consistent picture of the nodes reachable through itself to each routing region. A BR determines the routing information to propagate between different routing regions. Unclear how this relates to subneting and IP. I.e., this definition is imprecise. What is it that distinguishes a BR from some other type of router? Is this something determined dynamically? via static configuration? Or, how is a BR any different than a normal IP router? MANET Interface A MANET interface may demonstrate asymmetric reachability (e.g., SBI) and/or neighboring nodes' addresses may not be a priori known. Note: according to the definition of a classic IP interface, such an interface satisfies the characteristics of a MANET interface -- with the additional nice properties that it does not exhibit asymmetric reachability and a set of neighboring nodes' addresses are known a priori. The last part of this sentence seems incorrect. Most nodes do not know the set of neighboring node addresses. They may know an address prefix of destinations that can be assumed to be on-link, but that is not the same as what is written above. MANET Router (MNR) a MANET router embodies router functionality and may also include host functionality, reachable via its loopback interface(s). I don't understand this second part. A loopback interface is a software abstraction and is often implemented to look like an "interface" (oops, now I'm using the normal definition, not the manet one -- see why redefining this term confusing?). As such, you are now (presumably) talking about a particular implementation. As such, the above is not really an appropriate definition. A MANET router has one or more MANET interfaces. A MANET router may also have zero or more classic IP interfaces to which itself (via loopback), hosts, routers, or networks may connect; There is that funny loopback definition again. i.e. the router may be responsible for several IP prefixes. Hmm. now you are talking about IP addresses. A MANET router is expected to participate in routing on behalf of one or more of its interfaces. A MANET router is illustrated in Figure 1. also don't fully agree. and loopback terminology is weird. MANET a routing region consisting of a set of MANET routers that is within one or more MANET router hops. If a MANET connects to other routing regions, its border is defined by Border Routers. I don't understand what this means. E.g., how do you tell what is in one region and in another? Dependent upon the deployment and management strategy, coalescing and fragmentation of MANETs may be a supported feature. In other words, if a communication path between two previously separated MANET routers or MANETs becomes available, the two MANETs may merge to form a single larger MANET. Similarly, if a communication path between two MANET routers is disappears and no alternative path between the routers exists, then the MANET may be partitioned into two separate MANETs. Again, what does this mean? Why/how is this important? Does it impact the IP characteristics? If so, in what way? What are the implications (to IP) of a split or merge? Wireless interfaces exhibit challenging characteristics when compared to wired interfaces. Many protocols (e.g. IPv6 neighbor discovery [RFC2461]) do not operate in wireless networks with asymmetric reachability. Wireless interfaces also exhibit dynamic time varying performance (e.g. packet loss, data rate) that can significantly impact local communication. Um, this isn't a problem with "wireless" vs. "wired" interfaces per se, its a problem with links that display such non-standard characteristics. We need to be more precise! And to say "IP doesn't work well" is only true if you make some unstated assumptions about addresses/prefixes and how they are assigned. The act of forwarding packets out of the same interface as the one over which they were received often results in duplicate IP packets being received at MANET Routers with more than one neighboring MANET Router, while also reaching a new subset of MANET Routers. Thus, duplicate packet detection is often an inherent part of MANET protocol designs. Doesn't this depend on what LL address the packet contains? I'm not sure this statement is true. In wireless systems, nodes within the same small geographic region are often densely connected with other nearby nodes. These nodes form a set of extended neighbor relationships that is referred to as a neighborhood. A neighborhood is typically composed of several nodes, with each node being densely connected to other nodes. Is this an MANET Neighborhood? If not, is there a formal definition of neighborhood? 5.1. General Address Architecture This architectural model considers MANET routers as simply routers with addressable nodes attached, as illustrated in Figure 1. The Vague. What kind of addresses? IP? and what does "addressable node attached" mean? Link-local Multicast/Broadcast Scope On a MANET interface, a packet sent to a link-local multicast or broadcast addresses reaches the MANET interfaces of neighboring MANET routers, regardless of their configured addresses. Link- local packets are never forwarded and since a MANET may span several hops, nodes cannot assume that a packet sent to a link- local address will reach all MANET routers within a MANET. Are we talking IP or not? I don't know what "link local" means outside of the context of an IP link. But where is MANET defined to be an IP Link? Thomas _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www1.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Wed Sep 26 20:19: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 1Iah5o-0000Qi-Tl; Wed, 26 Sep 2007 20:19:00 -0400 Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1Iah5n-0000LC-NY for autoconf-confirm+ok@megatron.ietf.org; Wed, 26 Sep 2007 20:18:59 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iah5n-0000J1-D5 for autoconf@ietf.org; Wed, 26 Sep 2007 20:18:59 -0400 Received: from blv-smtpout-01.boeing.com ([130.76.32.69]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iah5f-0004tT-15 for autoconf@ietf.org; Wed, 26 Sep 2007 20:18:57 -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 l8R0IRrK024979 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 26 Sep 2007 17:18:28 -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 l8R0IRIh021265 for ; Wed, 26 Sep 2007 19:18:27 -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 l8R0IP8x021219 for ; Wed, 26 Sep 2007 19:18:27 -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); Wed, 26 Sep 2007 17:18:25 -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 Date: Wed, 26 Sep 2007 17:17:54 -0700 Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029EDAC8@XCH-NW-7V2.nw.nos.boeing.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: I-D Action:draft-templin-autoconf-dhcp-09.txt Thread-Index: Acf/0WZ4nwmdQjsJS5+Ek4JyoS5PewAygNKA From: "Templin, Fred L" To: X-OriginalArrivalTime: 27 Sep 2007 00:18:25.0865 (UTC) FILETIME=[EBF45B90:01C8009B] X-Spam-Score: 0.0 (/) X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976 Subject: [Autoconf] FW: I-D Action:draft-templin-autoconf-dhcp-09.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 FYI, a new version of this draft is available for comment (see below). Change log is as follows: Changes from -08 to -09: o Introduced the term "VET". o Changed address delegation language to speak of "MNBR-aggregated" instead of global/local. o Updated figures 1-3. o Explained why a MANET interface is "neutral". o Removed DHCPv4 "MLA Address option". Now, MNBRs can only be DHCPv4 servers; not relays. Fred fred.l.templin@boeing.com -----Original Message----- From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20 Sent: Tuesday, September 25, 2007 4:50 PM To: i-d-announce@ietf.org Subject: I-D Action:draft-templin-autoconf-dhcp-09.txt=20 A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : MANET Autoconfiguration Author(s) : F. Templin, et al. Filename : draft-templin-autoconf-dhcp-09.txt Pages : 20 Date : 2007-09-25 Mobile Ad-hoc Networks (MANETs) connect routers on links with asymmetric reachability characteristics, and may also connect to other networks including the Internet. Routers in MANETs must have a way to automatically provision IP addresses/prefixes and other information. This document specifies mechanisms for MANET autoconfiguration; both IPv4 and IPv6 are discussed. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-templin-autoconf-dhcp-09.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-templin-autoconf-dhcp-09.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-templin-autoconf-dhcp-09.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. _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www1.ietf.org/mailman/listinfo/autoconf