Re: [Autoconf] Closing summary on consensus-call for RFC5889modifications

reshmi r <reshmi.engg@gmail.com> Thu, 26 August 2010 04:17 UTC

Return-Path: <reshmi.engg@gmail.com>
X-Original-To: autoconf@core3.amsl.com
Delivered-To: autoconf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EC1FA3A6A7B for <autoconf@core3.amsl.com>; Wed, 25 Aug 2010 21:17:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level:
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id owfbMaBFG9ht for <autoconf@core3.amsl.com>; Wed, 25 Aug 2010 21:17:50 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 82C353A695B for <autoconf@ietf.org>; Wed, 25 Aug 2010 21:17:50 -0700 (PDT)
Received: by wwb28 with SMTP id 28so767066wwb.13 for <autoconf@ietf.org>; Wed, 25 Aug 2010 21:18:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=UsuT65X0Fog8my46hlQJv+aukTjZTWKCx/1MIvnEiko=; b=r/lSQ9CD+1M2xNcCaPCatkdHSpf4fcD2Bk/k6OnYkiVdDv5qQErE57337M1UFffnRZ rapghaHf3BFeUEp3qJv8gqhu1LbmHxlbZjsBPZpPtnZxrdfw24JC7MvOx65bkOGbfmaf HjVacEXUHqRtCADveLk++jQJOoSK49UK3lrJ0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=INlvsXdY3u5s2bW8ohYt1rXc3e3vMGEn1blJsObBd1umldppu2vwDyfFhFS9+zp0L+ WncUOoOmi1fVmIqGBogJ/KugDLkoyfQq6DCdIs5K3rkvgLaeayJkhvJovR8NPTxBZQPU MZVoGloggber9W/yStNX1F9O1Xgn25eipOKNc=
MIME-Version: 1.0
Received: by 10.227.146.213 with SMTP id i21mr8399707wbv.99.1282796302292; Wed, 25 Aug 2010 21:18:22 -0700 (PDT)
Received: by 10.227.40.210 with HTTP; Wed, 25 Aug 2010 21:18:22 -0700 (PDT)
In-Reply-To: <ABE739C5ADAC9A41ACCC72DF366B719D03609162@GLKMS2100.GREENLNK.NET>
References: <AANLkTi=MZORvNSW7wHdHYOzkOwNZojBars26GfSPgWc9@mail.gmail.com> <ABE739C5ADAC9A41ACCC72DF366B719D035CA5CE@GLKMS2100.GREENLNK.NET> <7ir5hoc4wq.fsf@lanthane.pps.jussieu.fr> <ABE739C5ADAC9A41ACCC72DF366B719D03609162@GLKMS2100.GREENLNK.NET>
Date: Thu, 26 Aug 2010 09:48:22 +0530
Message-ID: <AANLkTim8j=CG9ojk38oSAKZ++VR7Sp6GkcJOK4p9GprO@mail.gmail.com>
From: reshmi r <reshmi.engg@gmail.com>
To: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: autoconf@ietf.org
Subject: Re: [Autoconf] Closing summary on consensus-call for RFC5889modifications
X-BeenThere: autoconf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Ad-Hoc Network Autoconfiguration WG discussion list <autoconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/autoconf>, <mailto:autoconf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/autoconf>
List-Post: <mailto:autoconf@ietf.org>
List-Help: <mailto:autoconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/autoconf>, <mailto:autoconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Aug 2010 04:17:52 -0000

Christopher,

So it mean almost all the nodes replying to the routing messages will
be mentioned as router.
For eg: As we were discussing before, only some routing protocols like
OLSR support Multicast so only in that case you will have much
difference for a router and a node. In other cases all the nodes helps
in message unicasts and broadcasts so they all have to be mentioned as
router.

I may define a router as the node which runs a routing protocol in it,
then updates the routing information and send the routing informations
to other nodes. So here In those protocols which doesnot support
multicast every node acts as router.

Reshmi.T.R
Research Scholar,
Ramanujan Computing Center,
Anna University- Chennai,
Chennai, India

On Wed, Aug 25, 2010 at 2:11 PM, Dearlove, Christopher (UK)
<Chris.Dearlove@baesystems.com>; wrote:
> It's running the routing protocol, and not just listening
> to it, but engaging actively in it - sending necessary
> routing protocol messages. It's a router.
>
> --
> Christopher Dearlove
> Technology Leader, Communications Group
> Communications and Networks Capability
> BAE Systems Advanced Technology Centre
> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> Tel: +44 1245 242194  Fax: +44 1245 242124
>
> BAE Systems (Operations) Limited
> Registered Office: Warwick House, PO Box 87,
> Farnborough Aerospace Centre, Farnborough, Hants, GU14 6YU, UK
> Registered in England & Wales No: 1996687
>
> -----Original Message-----
> From: Juliusz Chroboczek [mailto:Juliusz.Chroboczek@pps.jussieu.fr]
> Sent: 24 August 2010 18:11
> To: Dearlove, Christopher (UK)
> Cc: reshmi r; autoconf@ietf.org
> Subject: Re: [Autoconf] Closing summary on consensus-call for
> RFC5889modifications
>
>
>                    *** WARNING ***
>
>  This message has originated outside your organisation,
>  either from an external partner or the Global Internet.
>      Keep this in mind if you answer this message.
>
>
>> consider for example an OLSR node that does not wish to be a relay,
>> only an endpoint. It can do that by setting WILLINGNESS equal to zero,
>> and if it is built only to take such a role it can then throw away
>> large chunks of OLSR code (for example it never sends TC messages).
>
> What you're describing is not a router.  It's a host that's snooping on
> a routing protocol.
>
>                                        Juliusz
>
>
> ********************************************************************
> This email and any attachments are confidential to the intended
> recipient and may also be privileged. If you are not the intended
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or
> distribute its contents to any other person.
> ********************************************************************
>
>