IETF Logo Mail Archive

Re: [Roll] Working Group Last Call:draft-ietf-roll-protocols-survey-02

"Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com> Mon, 08 December 2008 17:58 UTC

Return-Path: <roll-bounces@ietf.org>
X-Original-To: roll-archive@ietf.org
Delivered-To: ietfarch-roll-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ECB0D3A6951; Mon, 8 Dec 2008 09:58:36 -0800 (PST)
X-Original-To: roll@core3.amsl.com
Delivered-To: roll@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5437D28C120 for <roll@core3.amsl.com>; Mon, 8 Dec 2008 09:58:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.455
X-Spam-Level:
X-Spam-Status: No, score=-6.455 tagged_above=-999 required=5 tests=[AWL=0.144, BAYES_00=-2.599, 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 hIQtVG4cEoIG for <roll@core3.amsl.com>; Mon, 8 Dec 2008 09:58:35 -0800 (PST)
Received: from smtp1.bae.co.uk (smtp1.bae.co.uk [20.133.0.11]) by core3.amsl.com (Postfix) with ESMTP id 4744F3A6951 for <roll@ietf.org>; Mon, 8 Dec 2008 09:58:35 -0800 (PST)
Received: from smtpb.greenlnk.net (smtpb.greenlnk.net [10.15.160.219]) by smtp1.bae.co.uk (Switch-3.1.10/Switch-3.1.10) with ESMTP id mB8HwQMs021457 for <roll@ietf.org>; Mon, 8 Dec 2008 17:58:27 GMT
Received: from glkas0002.GREENLNK.NET (glkas0002.greenlnk.net [10.15.184.52]) by smtpb.greenlnk.net (Switch-3.1.9/Switch-3.1.9) with ESMTP id mB8HwQcv005208 for <roll@ietf.org>; Mon, 8 Dec 2008 17:58:26 GMT
Received: from glkms1100.GREENLNK.NET ([10.15.184.108]) by glkas0002.GREENLNK.NET with InterScan Message Security Suite; Mon, 08 Dec 2008 17:58:26 -0000
Received: from GLKMS2100.GREENLNK.NET ([10.15.184.93]) by glkms1100.GREENLNK.NET with Microsoft SMTPSVC(6.0.3790.2499); Mon, 8 Dec 2008 17:58:26 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 08 Dec 2008 17:58:24 -0000
Message-ID: <ABE739C5ADAC9A41ACCC72DF366B719D01652699@GLKMS2100.GREENLNK.NET>
In-Reply-To: <7471DA6B-7B09-42BB-8291-C30C83576295@cs.stanford.edu>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Roll] Working Group Last Call:draft-ietf-roll-protocols-survey-02
Thread-Index: AclZWrgyZNT2DiJ9S6ip4fl1DWknaAAAOUFg
References: <7C1A2E64-C1B0-472E-B354-77F290BBC80D@cisco.com><374005f30812050849refe8122i63629f469f8ba7c8@mail.gmail.com> <7471DA6B-7B09-42BB-8291-C30C83576295@cs.stanford.edu>
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Philip Levis <pal@cs.stanford.edu>, Ian Chakeres <ian.chakeres@gmail.com>
X-OriginalArrivalTime: 08 Dec 2008 17:58:26.0318 (UTC) FILETIME=[91B5D2E0:01C9595E]
Cc: charliep@computer.org, roll@ietf.org, arsalan@eecs.berkeley.edu
Subject: Re: [Roll] Working Group Last Call:draft-ietf-roll-protocols-survey-02
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/roll>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: roll-bounces@ietf.org
Errors-To: roll-bounces@ietf.org

> Your point about hierarchical addressing is interesting, and I think  
> it relates to comments others have made on fisheye routing and other  
> state suppression approaches.

Not quite. Hierarchical allocation is indeed a state suppression
approach. However fisheye is a control message suppression approach.

> Help me out if I'm mistaken here, but I  
> don't recall any work on address allocation/distribution in wireless  
> networks to enable good route aggregation.

There's work in the literature, but the relevant IETF WG (autoconf)
hasn't got to solutions yet.

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

_______________________________________________
Roll mailing list
Roll@ietf.org
https://www.ietf.org/mailman/listinfo/roll

v2.23.0 | Report a Bug | By Email