RE: [manet] few questions about MAC protocol
"Brijesh Kumar" <kumarb@research.panasonic.com> Wed, 27 October 2004 22:13 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21382 for <manet-web-archive@ietf.org>; Wed, 27 Oct 2004 18:13:20 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMwGi-0000cw-5C for manet-web-archive@ietf.org; Wed, 27 Oct 2004 18:27:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMvsK-00034l-By; Wed, 27 Oct 2004 18:02:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMvo6-0001GF-NX for manet@megatron.ietf.org; Wed, 27 Oct 2004 17:58:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19721 for <manet@ietf.org>; Wed, 27 Oct 2004 17:58:11 -0400 (EDT)
Received: from oak.research.panasonic.com ([150.169.1.4]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMw23-0000Jn-9D for manet@ietf.org; Wed, 27 Oct 2004 18:12:39 -0400
Received: from redwood.research.panasonic.com (redwood.research.panasonic.com [150.169.3.3]) by oak.research.panasonic.com (1.1.1/1.1.1) with SMTP id i9RLvhrG009281; Wed, 27 Oct 2004 17:57:43 -0400
Received: from redwood.research.panasonic.com (redwood.research.panasonic.com [150.169.3.3]) by testing.research.panasonic.com (Postfix) with ESMTP id 232763C80E2; Wed, 27 Oct 2004 17:55:51 -0400 (EDT)
Received: from Brijesh2K (dhcp251.Research.Panasonic.COM [150.169.1.251])by redwood.research.panasonic.com (Postfix) with SMTP id 18A183C80E1; Wed, 27 Oct 2004 17:55:51 -0400 (EDT)
From: Brijesh Kumar <kumarb@research.panasonic.com>
To: Parag Goswami <parag_intern@yahoo.com>, manet@ietf.org
Subject: RE: [manet] few questions about MAC protocol
Date: Wed, 27 Oct 2004 18:01:20 -0400
Message-ID: <NBEBKGCOLIBFGNGLINKHKEKODEAA.kumarb@research.panasonic.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
In-Reply-To: <20041027192955.74777.qmail@web90101.mail.scd.yahoo.com>
X-imss-version: 2.8
X-imss-result: Passed
X-imss-scores: Clean:99.90000 C:22 M:2 S:5 R:5
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
Sender: manet-bounces@ietf.org
Errors-To: manet-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit
Parag: It is a big area to explain. Here are some short answers, and pointers for you to explore further. >>Could anybody please tell me the anwere to these questions ? >> Why does the complexity in MAC protocol design for wireless ad hoc networks arises due to : >>1. node mobility Node mobility affects how time slots get allocated to existing nodes in the network/ or how often the contention will occur for the control of the channel. This directly affects throughput and energy efficiency of MAC protocols. >> 2. radio link vulnerability and Radio link vulnerability needs to be dealt with additional security mechanisms. The more information you put in a control channel, less you are left for data transmission. It has direct impact on efficiency of the MAC protocols. >>3. the lack of central coordination It is hard to obtain energy efficiency without central co-ordination. If no node tells you when to sleep and wake up to listen for incoming transmission, then you may have to listen to every frame from every one. That's not you want for large ad-hoc networks. Cheers, --bk _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet
- [manet] few questions about MAC protocol Parag Goswami
- RE: [manet] few questions about MAC protocol Brijesh Kumar