[manet] MANET Protocol Applicability
Abdussalam Baryun <abdussalambaryun@gmail.com> Fri, 08 June 2012 03:42 UTC
Return-Path: <abdussalambaryun@gmail.com>
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 8547311E80B3 for <manet@ietfa.amsl.com>; Thu, 7 Jun 2012 20:42:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.511
X-Spam-Level:
X-Spam-Status: No, score=-3.511 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 hztigyb4osBW for <manet@ietfa.amsl.com>; Thu, 7 Jun 2012 20:42:14 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id E052A21F8627 for <manet@ietf.org>; Thu, 7 Jun 2012 20:42:13 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so870996vbb.31 for <manet@ietf.org>; Thu, 07 Jun 2012 20:42:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=Lrp2gxmlLiivKyyr6XkDiKy3F+2kK7OYHJTJPO3y13o=; b=yWwJhKnS8oQfD01+Rbjhe9cRgcQkVTPhGIRfPwLwo6/O/JYpJ3tw/4BXOokmxak2md 5gw9ktq5BCDY/gUJfIE/+y63WR/PRgY7JmzuCU9a7RtaAWdQ5wsAaE7HMeBJPE4UKohE ufrCoCCovlY9q47q5SfIK6hW5dKEHc0nLJViomL1ygx1bEd24ZGmMvDyfSlCGxbrIEwB 50ntMg6dyIUy0/NnT7EDg/94pGSCl9UfgjUQ0KAVjpktSSXMQDyCa5+f+V12yKN5QYtA FSXYjnNTgK+5XGKd3iQIOxPszauKGfsCkiJLnX0wgu42gs+ZZsndJDVA3dZHEbMP/deF hDHg==
MIME-Version: 1.0
Received: by 10.52.94.36 with SMTP id cz4mr4115695vdb.10.1339126933196; Thu, 07 Jun 2012 20:42:13 -0700 (PDT)
Received: by 10.220.98.77 with HTTP; Thu, 7 Jun 2012 20:42:13 -0700 (PDT)
Date: Fri, 08 Jun 2012 05:42:13 +0200
Message-ID: <CADnDZ89+0oWbJU_khgmn8pDKcWCm6dTJZiEw8hjFqggAoPkkrg@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: manet <manet@ietf.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Subject: [manet] MANET Protocol Applicability
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Fri, 08 Jun 2012 03:42:14 -0000
Hi Folks I have read two important inputs and want to share my opinion, ============ point 1 ============ In one work in progress ietf-draft (expired): draft-ietf-manet-appl-00.txt, Corson, (1998)mentioned in Abstract and Introduction: Abstract> The intent of this ’Applicability Section’ is to aid readers unfamiliar with the details of each protocol’s design in understanding the protocol’s basic characteristics, functioning and mechanisms, as well as to provide a general description of the networking context for which the protocol was designed, and in which it is expected to perform well. Introduction> The set of applications for which the use of MANET technology envisioned is diverse, ranging from small, energy-constrained nearly static networks to large-scale, mobile, highly-dynamic networks. The combinations of network size, topology composition and dynamics, bandwidth and energy availability, physical and link-layer technologies, intended application usages, etc. are many, and it seems unlikely that a single protocol will function superiorly over this wide range of networking contexts. Thus a given protocol is likely to be well-suited for operation in those networks whose characteristics match well with the combination of mechanisms employed by the protocol. ============ point 2 ============== In the MANET WG 77 meeting minutes, Mr.Clausen mentioned that it is important to be explicit about assumptions/conditions before talking about protocol. ============ opinion ============== I agree with both points and approach to solve routing protocols, and would RECOMMEND either of the following: 1- MANET WG defines (in one informative-draft) intended application usage, and be explicit about applicable L2 network technologies. So that each future protocols mentions in their applicability statement section the usual use-case for such protocol, OR 2- MANET WG renews the I-D expired of Corson (1998) and adds more issues so it can become an RFC in future, Thanking you, Abdussalam Baryun =========================
- [manet] MANET Protocol Applicability Abdussalam Baryun
- Re: [manet] MANET Protocol Applicability Dearlove, Christopher (UK)
- Re: [manet] MANET Protocol Applicability John Dowdell
- Re: [manet] MANET Protocol Applicability Teco Boot
- Re: [manet] MANET Protocol Applicability Abdussalam Baryun
- Re: [manet] MANET Protocol Applicability Abdussalam Baryun
- Re: [manet] MANET Protocol Applicability Dearlove, Christopher (UK)
- Re: [manet] MANET Protocol Applicability Henning Rogge
- Re: [manet] MANET Protocol Applicability Teco Boot
- Re: [manet] MANET Protocol Applicability Stan Ratliff
- Re: [manet] MANET Protocol Applicability Abdussalam Baryun
- Re: [manet] MANET Protocol Applicability Abdussalam Baryun