Re: [Autoconf] aspects of multi-hop wireless communication

"Emmanuel Baccelli" <Emmanuel.Baccelli@inria.fr> Fri, 19 December 2008 15:21 UTC

Return-Path: <autoconf-bounces@ietf.org>
X-Original-To: autoconf-archive@megatron.ietf.org
Delivered-To: ietfarch-autoconf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AEEA53A6A35; Fri, 19 Dec 2008 07:21:47 -0800 (PST)
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 1ED4E3A6A3F for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 07:21:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.916
X-Spam-Level:
X-Spam-Status: No, score=-1.916 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 HX5LgO9Prz35 for <autoconf@core3.amsl.com>; Fri, 19 Dec 2008 07:21:45 -0800 (PST)
Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.186]) by core3.amsl.com (Postfix) with ESMTP id CEEDF3A69F9 for <autoconf@ietf.org>; Fri, 19 Dec 2008 07:21:44 -0800 (PST)
Received: by fk-out-0910.google.com with SMTP id 18so552954fkq.5 for <autoconf@ietf.org>; Fri, 19 Dec 2008 07:21:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type:references :x-google-sender-auth; bh=j2wk7aiEntkXbT/hURKFmkSZ+GwHiC/Qk8A+uEeiILo=; b=cvrumZnOzGmFFS9/5oJuEV8ytGtTufy+hIQXVidkePZiEpaFC/vf4jf9Ny1yo18KfO 4KG1KnjCD2K06Qs78gw30Dx6BOSARVK0P2deVGav35Z1BaQCYVrvmDdW9esQD43ULxd1 iU114EMgDuhcB6QQLdl0BOh44PByDIfg3UHKo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:references:x-google-sender-auth; b=e801zUMM2U2kRe4kT1bUsw2SJIl4JPBsz4otCgHTiFOoo2zBFTNJniWfqVOho2O6+n xm6IR1bxgLal8NiDEkgYEAhd1QrOfc++6ncTD/Ts65ZxUrcfdJhCIZpk0Uwhyc96/uFk oX3zueHvllCMQF2+86ZeKv/56191xEFmcwCfs=
Received: by 10.102.247.4 with SMTP id u4mr1263029muh.104.1229700095538; Fri, 19 Dec 2008 07:21:35 -0800 (PST)
Received: by 10.103.248.12 with HTTP; Fri, 19 Dec 2008 07:21:35 -0800 (PST)
Message-ID: <be8c8d780812190721r7ea9c43aif8aff7c83f44f43@mail.gmail.com>
Date: Fri, 19 Dec 2008 16:21:35 +0100
From: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>
To: autoconf@ietf.org
In-Reply-To: <ABE739C5ADAC9A41ACCC72DF366B719D016C3E14@GLKMS2100.GREENLNK.NET>
MIME-Version: 1.0
References: <be8c8d780812190119r200efceawef79c63766ea1a3f@mail.gmail.com> <494B8E7C.7000505@gmail.com> <be8c8d780812190504x98496egc37c25b21a799ceb@mail.gmail.com> <494BB75E.4050206@gmail.com> <ABE739C5ADAC9A41ACCC72DF366B719D016C3E14@GLKMS2100.GREENLNK.NET>
X-Google-Sender-Auth: 05ab24bfaa1c4e62
Subject: Re: [Autoconf] aspects of multi-hop wireless communication
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0229219854=="
Sender: autoconf-bounces@ietf.org
Errors-To: autoconf-bounces@ietf.org

On Fri, Dec 19, 2008 at 4:06 PM, Dearlove, Christopher (UK) <
chris.dearlove@baesystems.com> wrote:

>
> > I think some solutions exist at PHY and MAC layers in the case of
> 802.11.
>
> As has been said many times before, MANET is not just
> about 802.11.
>

I think Chris makes an important point here.
We are discussing things experienced at the IP layer.
The draft is not saying "there is a need for a solution".
The draft is saying "this is what is often observed".
That's it. I think we can agree on this ;)

Emmanuel
_______________________________________________
Autoconf mailing list
Autoconf@ietf.org
https://www.ietf.org/mailman/listinfo/autoconf