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

"Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com> Tue, 24 August 2010 08:55 UTC

Return-Path: <Chris.Dearlove@baesystems.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 814583A6767 for <autoconf@core3.amsl.com>; Tue, 24 Aug 2010 01:55:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.403
X-Spam-Level:
X-Spam-Status: No, score=-5.403 tagged_above=-999 required=5 tests=[AWL=-1.404, BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0KtorabOPvMj for <autoconf@core3.amsl.com>; Tue, 24 Aug 2010 01:55:22 -0700 (PDT)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by core3.amsl.com (Postfix) with ESMTP id 378023A6782 for <autoconf@ietf.org>; Tue, 24 Aug 2010 01:55:22 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.56,262,1280703600"; d="scan'208";a="83525955"
Received: from unknown (HELO baemasodc004.greenlnk.net) ([10.108.36.11]) by Baemasodc001ir.sharelnk.net with ESMTP; 24 Aug 2010 09:55:54 +0100
Received: from glkms1102.GREENLNK.NET (glkms1102.greenlnk.net [10.108.36.193]) by baemasodc004.greenlnk.net (Switch-3.4.3/Switch-3.4.3) with ESMTP id o7O8trpU028841; Tue, 24 Aug 2010 09:55:54 +0100
Received: from GLKMS2100.GREENLNK.NET ([10.15.184.93]) by glkms1102.GREENLNK.NET with Microsoft SMTPSVC(6.0.3790.4675); Tue, 24 Aug 2010 09:55:53 +0100
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: 7bit
Date: Tue, 24 Aug 2010 09:55:53 +0100
Message-ID: <ABE739C5ADAC9A41ACCC72DF366B719D035CA5CE@GLKMS2100.GREENLNK.NET>
In-Reply-To: <AANLkTi=MZORvNSW7wHdHYOzkOwNZojBars26GfSPgWc9@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Autoconf] Closing summary on consensus-call for RFC5889modifications
Thread-Index: ActDRxfR4YzF8cZTTl+KHn3/Ir3/bAAIaUig
References: <AANLkTi=MZORvNSW7wHdHYOzkOwNZojBars26GfSPgWc9@mail.gmail.com>
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
To: "reshmi r" <reshmi.engg@gmail.com>, <autoconf@ietf.org>
X-OriginalArrivalTime: 24 Aug 2010 08:55:53.0915 (UTC) FILETIME=[28BB50B0:01CB436A]
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: Tue, 24 Aug 2010 08:55:23 -0000

I think there's a misunderstanding here. All the way back to RFC 2501,
a node has been defined as a router plus possible hosts. If you've got
a wireless device that wants to participate in a MANET it needs to be
running an ad hoc routing protocol, i.e. it's a router. It may perform
only a limited subset of routing functions - 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). But the node still has some
router functions. This is the model of both RFC 2501 and 5889-to-be.
The host can then get its addresses in any non-MANET-specific way on
that node.

-- 
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: autoconf-bounces@ietf.org [mailto:autoconf-bounces@ietf.org] On
Behalf Of reshmi r
Sent: 24 August 2010 05:45
To: 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.
 

Hi Teco,

Do they really mean a model for the autoconfiguration and is there is
no role for host in autoconfiguration??........the topic goes in to
real debate. what was the final outcome of the discussion???.

Hi All,

Can anyone finalise the suggested outcomes of the discussion??Do you
all really mean that the routers only need to do the autoconfiguration
and the nodes have no role in it??? If so how can we believe a router
to be genuine and how can we ensure that the router will never become
selfish??? so there should be some role in hosts to monitor the
traffic behaviour of router and the host should be able to notify with
some protocol mechanism. do you all really mean to change the title???
I strongly disagree with this.


Rgds,
Reshmi.


Hi Thomas,

On the title change, I remember in Maastricht all accept one
preferred the title change. On the list as well.
There are two arguments.
1) it is _a_ model
2) the model doesn't support hosts, or at least not very well
On the latter, there was a discussion without outcome.

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


********************************************************************
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.
********************************************************************