Re: [manet] Why the WG Reactive Protocol to be Compatible with another?

Abdussalam Baryun <abdussalambaryun@gmail.com> Wed, 20 February 2013 16:49 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 1ADA221F87CC for <manet@ietfa.amsl.com>; Wed, 20 Feb 2013 08:49:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.239
X-Spam-Level:
X-Spam-Status: No, score=-3.239 tagged_above=-999 required=5 tests=[AWL=-0.240, BAYES_00=-2.599, J_CHICKENPOX_46=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HjHp4qv5eQFI for <manet@ietfa.amsl.com>; Wed, 20 Feb 2013 08:49:05 -0800 (PST)
Received: from mail-pb0-f45.google.com (mail-pb0-f45.google.com [209.85.160.45]) by ietfa.amsl.com (Postfix) with ESMTP id 8DB9921F87B1 for <manet@ietf.org>; Wed, 20 Feb 2013 08:49:05 -0800 (PST)
Received: by mail-pb0-f45.google.com with SMTP id ro8so2971311pbb.18 for <manet@ietf.org>; Wed, 20 Feb 2013 08:49:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=0/9nWqzSIU67lBNrgywM4JIczp6unxjuf+GL93ze80k=; b=O+ePgwhMLkXhUYOpu1QdhdqgRmZquRozbTGqpYp3Ua9g4hTSl0NDL/d4a0BF4+14fm rSd+Scq7GauvCGq6GQFPsPcIscxotWMqQvAnDhtmuHJL5LcRBw9BRcakcXIl9c+1sWaP +BS186chQxWYTIMM7ZwuxQ18Fzh0RjXdx+jqKihHhU99HVyrMVlvfvDTi02Sezcy9hd9 UbB5E7R/Y4gawcfygv24K41AfOj2zRkxQTHnEZR2yKThR4hgR5fYOe0gW2Oe0fv8db78 p+UwE4E5F7u948briNTWkTDeDYnFelsE5/1mKxMpqWvpaKFv0N2hQX5584kRNd40yfNA OSTA==
MIME-Version: 1.0
X-Received: by 10.66.185.33 with SMTP id ez1mr3346093pac.93.1361378945351; Wed, 20 Feb 2013 08:49:05 -0800 (PST)
Received: by 10.68.33.132 with HTTP; Wed, 20 Feb 2013 08:49:05 -0800 (PST)
In-Reply-To: <03B78081B371D44390ED6E7BADBB4A77232CA63D@xmb-rcd-x02.cisco.com>
References: <CADnDZ89R_L4=inUn6_yW5R0jY933orBdYfbLyvp8pZfpPGJWOQ@mail.gmail.com> <03B78081B371D44390ED6E7BADBB4A77232CA63D@xmb-rcd-x02.cisco.com>
Date: Wed, 20 Feb 2013 17:49:05 +0100
Message-ID: <CADnDZ8-he2z00UA8qV=aKvVkaQ3jB5fG-hmixBAcZ9YM0x80PA@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "JP Vasseur (jvasseur)" <jvasseur@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] Why the WG Reactive Protocol to be Compatible with another?
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: Wed, 20 Feb 2013 16:49:06 -0000

Hi JP,

Yes that was my first discussion approach (the best technical features
to be adopted in the WG protocol), but seen some inputs that our
reactive protocol to be compatible to another, and I thought why the
other don't be compatible to this which I needed an answer. I agree
that we will waste time if we choose to make our work compatible to
other reactive protocol or as you mention it will be non sense. In
addition, it needs to use RFC5444 (was discussed) and also to be
compatible to NHDP,

AB

On 2/20/13, JP Vasseur (jvasseur) <jvasseur@cisco.com> wrote:
> Hi AB,
>
> This is critical topic and I cannot agree more with you; the objective is in
> my opinion to come up with the best protocol for the IETF.
> Let's be clear: the objective of the IETF is to produce qualitative
> protocols for the best of the IETF community and industry, not to make
> X or Y happy. Every single good ideas borrowed from Load should in my
> opinion be adopted by AODVv2, if there is a consensus. On the
> other hand, trying to design AODVv2 with the constraint of making it
> compatible with another protocol is a COMPLETE non sense.
>
> Thanks.
>
> JP.
>
> On Feb 20, 2013, at 3:03 AM, Abdussalam Baryun wrote:
>
> Hi Folks,
>
> I am not sure why we will make effort of AODVv2 compatible with
> LOADng, I am trying to find a good reason mentioned in the WG. I seen
> the intention by some participants, but not sure was it intention to
> merge DYMO+LOADng without compatibility (with either DYMO or LOADng)
> or with percentage of compatibility. Do you think it is good way to
> make the reactive protocol and then try to make it compatible?  Please
> advise,
>
> I will have to agree with the below proposal, that if the WG is
> agreeing to make compatible with LOADng, then why not go for 100%
> compatibility, just change the name title.
>
> AB
>
> Sub:Re: [manet] Reactive protocol decision process, for the record thoughts
> On 2/16/13, Ulrich Herberg <ulrich@herberg.name<mailto:ulrich@herberg.name>>
> wrote:
> Justin,
>
> I very much agree with you, Justin. One point I would like to add is
> that the WG will now spend a lot of time making the new AODVv2
> compatible with LOADng (which is claimed in the current DYMO draft);
> that is, in my opinion, a wasted effort since the LOADng draft is per
> definition 100% compatible with LOADng (had that been the starting
> point).
> Ignoring a document that has multiple interoperable implementations,
> deployments, MIB document, as well a support from at least a dozen
> MANET participants (not only LOADng authors) without giving rational
> was a disappointment for me.
>
> Best regards
> Ulrich
>
> _______________________________________________
> manet mailing list
> manet@ietf.org<mailto:manet@ietf.org>
> https://www.ietf.org/mailman/listinfo/manet
>
>