From autoconf-bounces@ietf.org Wed May 09 04:53:30 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HlhvO-0006pe-LL; Wed, 09 May 2007 04:53:30 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HlhvN-0006pV-Ce for autoconf@ietf.org; Wed, 09 May 2007 04:53:29 -0400 Received: from web31801.mail.mud.yahoo.com ([68.142.207.64]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HlhvL-000403-SC for autoconf@ietf.org; Wed, 09 May 2007 04:53:29 -0400 Received: (qmail 23414 invoked by uid 60001); 9 May 2007 08:53:27 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=0bWNKvC1gim4qsw5awHWHO4VRaWvEVEMtqZuA4698i2EvU03T8jsCPQdWu1tKZK3rlK1JeSctxzH2+kENlyBwr34uorK1afVYtByqnQgAj/AUAD3gPGgF8IYwEsAry5jvnshvMzjhFcm8wBUdh0y4hiFuimqsZdh/J/8TU1HGQo=; X-YMail-OSG: g_tKVdsVM1n3zGVGO19mBpWlYH9BDdAyI3OB783QaFV2dhXGwsEJxfFaIF53GaXuoYM5BYn2RtcCJsLumniBwBJcv3uFv3WBUziEHSQIfBibE.cBc9dzCq0ezwPmjA-- Received: from [59.165.148.20] by web31801.mail.mud.yahoo.com via HTTP; Wed, 09 May 2007 01:53:27 PDT Date: Wed, 9 May 2007 01:53:27 -0700 (PDT) From: Harish Kumar To: autoconf@ietf.org MIME-Version: 1.0 Message-ID: <261545.23252.qm@web31801.mail.mud.yahoo.com> X-Spam-Score: 0.5 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Subject: [Autoconf] Simulation on Ns-2 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="===============0748358160==" Errors-To: autoconf-bounces@ietf.org --===============0748358160== Content-Type: multipart/alternative; boundary="0-2050410427-1178700807=:23252" Content-Transfer-Encoding: 8bit --0-2050410427-1178700807=:23252 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Can any body help in simulating various address assignment methods in MANET on ns-2? Harish --------------------------------- Get your own web address. Have a HUGE year through Yahoo! Small Business. --0-2050410427-1178700807=:23252 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
Can any body help in simulating various address assignment methods in MANET on ns-2?
 
Harish

Get your own web address.
Have a HUGE year through Yahoo! Small Business. --0-2050410427-1178700807=:23252-- --===============0748358160== 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 --===============0748358160==-- From autoconf-bounces@ietf.org Thu May 10 02:48:09 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hm2Rd-00033h-2X; Thu, 10 May 2007 02:48:09 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hm2Rc-00033c-6Y for autoconf@ietf.org; Thu, 10 May 2007 02:48:08 -0400 Received: from py-out-1112.google.com ([64.233.166.183]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hm2Rb-0005hI-03 for autoconf@ietf.org; Thu, 10 May 2007 02:48:08 -0400 Received: by py-out-1112.google.com with SMTP id f31so379278pyh for ; Wed, 09 May 2007 23:48:06 -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:content-transfer-encoding:content-disposition; b=k+0SGLRDT4cAKya2y/AMwVbvEnYrNubtIV8i7RMVGhWG0kjpXtOh4wBX8tT0853VNeNcoQ7p6WlZr7xmfoaouRj2js2DzIx54rHbXf0AWc1W3hAxQ4lW8H+eKcgGn68aV+NW3SRtk/ge/qfq6BZhKyfcWRRfPpIkVMlDe9GPZ0k= 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=Lt2xmfhlM/XgNw5Xk2SLHz4wMBQF4kwCkVyt3w9sFkKgyesk5ccz5j5Z3etRlEQivzxP9qG3kxdjNCjrdDHy0/BB8sQ6/VX316IYfp76LEelwxgfeGamczVXnyGusacmURmiobIijav/s2hn3ModzzWQbGcap3HyMQP5qY4TfmM= Received: by 10.35.134.19 with SMTP id l19mr2521239pyn.1178779686708; Wed, 09 May 2007 23:48:06 -0700 (PDT) Received: by 10.35.38.20 with HTTP; Wed, 9 May 2007 23:48:06 -0700 (PDT) Message-ID: <2a3692de0705092348j48477a11re246b5cc9749026b@mail.gmail.com> Date: Thu, 10 May 2007 15:48:06 +0900 From: "Dominik Kaspar" To: autoconf@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Subject: [Autoconf] MANET Node Terminology (draft-ietf-autoconf-manetarch-01) 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, In draft-ietf-autoconf-manetarch-01 a node is defined as "any device (router or host) that implements IP" and a MANET node is defined as "a MANET node embodies a MANET router and zero or more hosts". If I understand correctly, a "node" is a single physical device (with a single MAC address), while a "MANET node" is a network of physical devices (hosts) connected in a star-topology fashion to a single MANET router. I find it very confusing that the terminology of a node is "borrowed" to define a "MANET node", which is actually not a single, but potentially many nodes. Greetings, Dominik _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www1.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Fri May 11 09:27: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 1HmV9j-0004gn-T0; Fri, 11 May 2007 09:27:35 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmV9j-0004gi-3M for autoconf@ietf.org; Fri, 11 May 2007 09:27:35 -0400 Received: from mailout1.samsung.com ([203.254.224.24]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HmV9g-0001Gu-K5 for autoconf@ietf.org; Fri, 11 May 2007 09:27:35 -0400 Received: from epmmp2 (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 <0JHV00CPAPDU8V@mailout1.samsung.com> for autoconf@ietf.org; Fri, 11 May 2007 22:27:30 +0900 (KST) Received: from Shubhranshu ([107.108.4.124]) by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTPA id <0JHV0078UPDT5O@mmp2.samsung.com> for autoconf@ietf.org; Fri, 11 May 2007 22:27:30 +0900 (KST) Date: Fri, 11 May 2007 19:03:23 +0530 From: Shubhranshu To: Dominik Kaspar Message-id: <011601c793d0$f3802250$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: 0.1 (/) X-Scan-Signature: 73734d43604d52d23b3eba644a169745 Cc: autoconf@ietf.org Subject: [Autoconf] Re:MANET Node Terminology (draft-ietf-autoconf-manetarch-01) 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="===============1333100551==" Errors-To: autoconf-bounces@ietf.org This is a multi-part message in MIME format. --===============1333100551== Content-type: multipart/alternative; boundary="Boundary_(ID_iYgpxfp/I6x6BhhDkp9hOg)" This is a multi-part message in MIME format. --Boundary_(ID_iYgpxfp/I6x6BhhDkp9hOg) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Hello Dominik, ----- Original Message ----- From: "Dominik Kaspar" To: Sent: Thursday, May 10, 2007 12:18 PM Subject: [Autoconf] MANET Node Terminology (draft-ietf-autoconf-manetarch-01) > Hello, > > In draft-ietf-autoconf-manetarch-01 a node is defined as "any device > (router or host) that implements IP" and a MANET node is defined as "a > MANET node embodies a MANET router and zero or more hosts". > > If I understand correctly, a "node" is a single physical device (with > a single MAC address), while a "MANET node" is a network of physical > devices (hosts) connected in a star-topology fashion to a single MANET > router. > > I find it very confusing that the terminology of a node is "borrowed" > to define a "MANET node", which is actually not a single, but > potentially many nodes. > Actually No, "MANET node" is not defined to mean potentially many nodes. Also, above MANET node definition does not include network aspect; it only says that host(s) may or may not be connected to a MANET router, which could have one or more physical/logical interfaces. - Shubhranshu --Boundary_(ID_iYgpxfp/I6x6BhhDkp9hOg) Content-type: text/html; charset=iso-8859-1 Content-transfer-encoding: 7BIT
Hello Dominik,
 
----- Original Message -----
From: "Dominik Kaspar" <dokaspar.ietf@gmail.com>
Sent: Thursday, May 10, 2007 12:18 PM
Subject: [Autoconf] MANET Node Terminology (draft-ietf-autoconf-manetarch-01)

 
> Hello,
>
> In draft-ietf-autoconf-manetarch-01 a node is defined as "any device
> (router or host) that implements IP" and a MANET node is defined as "a
> MANET node embodies a MANET router and zero or more hosts".
>
> If I understand correctly, a "node" is a single physical device (with
> a single MAC address), while a "MANET node" is a network of physical
> devices (hosts) connected in a star-topology fashion to a single MANET
> router.
>
> I find it very confusing that the terminology of a node is "borrowed"
> to define a "MANET node", which is actually not a single, but
> potentially many nodes.
>
 
Actually No, "MANET node" is not defined to mean potentially many nodes.
Also, above MANET node definition does not include network aspect;
it only says that host(s) may or may not be connected to a MANET router,
which could have one or more physical/logical interfaces.
 
 
- Shubhranshu 
 

 
--Boundary_(ID_iYgpxfp/I6x6BhhDkp9hOg)-- --===============1333100551== 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 --===============1333100551==-- From autoconf-bounces@ietf.org Sat May 12 03:24:38 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hmly2-00057t-0e; Sat, 12 May 2007 03:24:38 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hmly0-00057L-MC for autoconf@ietf.org; Sat, 12 May 2007 03:24:36 -0400 Received: from mu-out-0910.google.com ([209.85.134.185]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hmlvj-0007IW-B4 for autoconf@ietf.org; Sat, 12 May 2007 03:22:17 -0400 Received: by mu-out-0910.google.com with SMTP id g7so749584muf for ; Sat, 12 May 2007 00:22:14 -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:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=aHb3NoP48rp/SpNZdiuaYywUZVkdnvrCaHvVhS/M4dZJGcQCh4+RckAmChK2jcfgO0jdWKGdVs/dOyqfmYDRwZ64MZ/3fpuk/5fHTEpmfQrUX/K6h9hM5NQ2eCHrzeQJP9x0VIfUVJAczsHYwJvXx0sT9Pf0XjRg7kTnrjuf2jQ= 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=GiGKdK9obpYdsGtIpvPBkIOIlvsONO+SLhnDZnFKlPdJr09lpUB1uiaCPK/HdeHLYxrjF3uwQtntaf5G1c4BEqsh5mjfiJGqiqUGxc7HQy0l1C/hn6rZAgyq5fViqmWmRv+Uw7UYZcghgSOGsJ2pfEmxIjiPZRYcdsSGDDj+Q/c= Received: by 10.78.179.12 with SMTP id b12mr1101701huf.1178954534441; Sat, 12 May 2007 00:22:14 -0700 (PDT) Received: by 10.78.33.14 with HTTP; Sat, 12 May 2007 00:22:14 -0700 (PDT) Message-ID: <374005f30705120022i6a347ceeid30bf8a8da529284@mail.gmail.com> Date: Sat, 12 May 2007 12:52:14 +0530 From: "Ian Chakeres" To: "Dominik Kaspar" Subject: Re: [Autoconf] MANET Node Terminology (draft-ietf-autoconf-manetarch-01) In-Reply-To: <2a3692de0705092348j48477a11re246b5cc9749026b@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a3692de0705092348j48477a11re246b5cc9749026b@mail.gmail.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Cc: autoconf@ietf.org, "Singh Shubhranshu \(home\)" 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 If you look at Figure 1 it is a little more explicit. That said, I agree the text is a little unclear. We are in the process of cleaning it up, and the next revision will be more explicit. Ian On 5/10/07, Dominik Kaspar wrote: > Hello, > > In draft-ietf-autoconf-manetarch-01 a node is defined as "any device > (router or host) that implements IP" and a MANET node is defined as "a > MANET node embodies a MANET router and zero or more hosts". > > If I understand correctly, a "node" is a single physical device (with > a single MAC address), while a "MANET node" is a network of physical > devices (hosts) connected in a star-topology fashion to a single MANET > router. > > I find it very confusing that the terminology of a node is "borrowed" > to define a "MANET node", which is actually not a single, but > potentially many nodes. > > Greetings, > Dominik > > _______________________________________________ > 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 Thu May 31 18:50:55 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HttTq-0000D6-HF; Thu, 31 May 2007 18:50:54 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HttTV-00084m-Ty; Thu, 31 May 2007 18:50:34 -0400 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HttTU-0007VN-HY; Thu, 31 May 2007 18:50:33 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 76380175F1; Thu, 31 May 2007 22:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HttT0-0003Fe-4E; Thu, 31 May 2007 18:50: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, 31 May 2007 18:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Cc: autoconf@ietf.org Subject: [Autoconf] I-D ACTION:draft-ietf-autoconf-manetarch-02.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-02.txt Pages : 20 Date : 2007-5-31 This document discusses Mobile Ad hoc NETworks (MANETs). It introduces basic MANET terms, characteristics, and challenges. This document also defines several MANET entities and architectural concepts. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-autoconf-manetarch-02.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-02.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-02.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-5-31161011.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-autoconf-manetarch-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-autoconf-manetarch-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-5-31161011.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--