IETF Logo Mail Archive

[manet] A view on packet-BB

"Charles E. Perkins" <charliep@computer.org> Thu, 29 March 2012 14:31 UTC

Return-Path: <charliep@computer.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD07021E81B3 for <manet@ietfa.amsl.com>; Thu, 29 Mar 2012 07:31:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yHNoeZId53R0 for <manet@ietfa.amsl.com>; Thu, 29 Mar 2012 07:31:02 -0700 (PDT)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by ietfa.amsl.com (Postfix) with ESMTP id 7559D21E81AF for <manet@ietf.org>; Thu, 29 Mar 2012 07:31:02 -0700 (PDT)
Received: from [130.129.83.71] by elasmtp-banded.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <charliep@computer.org>) id 1SDGNP-0004xZ-9q for manet@ietf.org; Thu, 29 Mar 2012 10:30:59 -0400
Message-ID: <4F74722A.6060703@computer.org>
Date: Thu, 29 Mar 2012 07:31:06 -0700
From: "Charles E. Perkins" <charliep@computer.org>
Organization: Wichorus Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Manet <manet@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956d5d4673fe7faad866a49cfaf4b0a7edaae07b21bf67774a3350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 130.129.83.71
Subject: [manet] A view on packet-BB
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: charliep@computer.org
List-Id: Mobile Ad-hoc Networks <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Mar 2012 14:31:03 -0000

Hello folks,

I have not participated very much in any discussions about
packet-BB other than to encourage header size reduction and
offer a few suggestions about how to achieve it.  During that
time, it was claimed that for many networks of interest, the
use of packet-BB would *decrease* header size, perhaps
especially for proactive protocols.  This is a question
very suitable for resolution by way of simulation.

If, as I suspect, packet-BB does (on average) introduce
header enlargement on some networks that cannot afford it,
I would be in favor to introduce the option to run AODV
(or OLSR, for that matter) with some sort of "reduced"
header.  This should only be deployed in networks where
otherwise there would be no feasible deployment of an
ad-hoc networking protocol.  From that perspective, it's
almost a no brainer -- either deploy the standard stripped-
down version, or deploy something else nonstandard that
looks exactly like the stripped-down version.

In summary, if there are cases where the [manet] protocols
can only be deployed without packet-BB header overhead,
then I think we should provide a solution for those cases.

To be clear, I am happy either way, whether or not packet-BB
headers are mandates in all cases.

Also, to be clear, we can standardize AODVv2 *with* packet-BB
right now, and submit for consideration another document for
AODVv2 that does not require packet-BB.  Or, we can enable both
ways in the next revision.  Or, we can standardize AODVv2
that does NOT use packet-BB, and then submit for consideration
another document that DOES use packet-BB.  All cases are just
fine with me, depending on what the working group wants.

Regards,
Charlie P.

v2.23.0 | Report a Bug | By Email