Re: [manet] AODVv2 implementation

Abdussalam Baryun <> Sun, 28 January 2024 22:19 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 43B4EC14F69B for <>; Sun, 28 Jan 2024 14:19:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id wmnGiiUlL4Qt for <>; Sun, 28 Jan 2024 14:19:20 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::42d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by (Postfix) with ESMTPS id ADFBBC14F60C for <>; Sun, 28 Jan 2024 14:19:20 -0800 (PST)
Received: by with SMTP id ffacd0b85a97d-337cf4eabc9so1935233f8f.3 for <>; Sun, 28 Jan 2024 14:19:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20230601; t=1706480359; x=1707085159;; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=sMgCiotpAgmhM+KpG3Mr25drt1AInwNd4ZE5dgYdVAA=; b=ZMXuTzuYko6AryH7+u+/lNvMiFCCelnIs5kjdTrr0iRelOb9+/xxQayo6hIU3gOnt1 nQUNhwEKrqeoJm/Fb1reaVLzHSPMDEpwG/kRmuwvcZD74WKxZ/VPNfygL3fx+JBpwaGB RcDWr7cFH5yYxGgEd+KUYyZ4PmaL1XbigH0FNHZweXuTciYXyT4iBX9/1FNVL7wKUnaw ulZJ3esISRY8kxHvIKH7VGxBfEUwJ9mMUSUCkKiMiOOmW7Tdv3GQYfRIo310dHI93JRf Z4wHfe1YJ7TgLbM0TaxyQOz8Cg82PBl1iVW/p3JB38UzSzv3JN5OjWUTk7QTQLZxt2p7 6U8Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20230601; t=1706480359; x=1707085159; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=sMgCiotpAgmhM+KpG3Mr25drt1AInwNd4ZE5dgYdVAA=; b=fnB07pJbfmf7JcbXb8xUHyiWv5TN9ccVsF0EKNHFnVan8kzo+xcSdN98gAaEbkZcCv 3TsLU2sB75hpHwMcJWKv5m3GjjwzQZn2l6OBbP6pRZLUA4gQkKY+/N8cRUhnfDKG0LGq JPgwX+hIetjHJQE9iLqdbKQ3/RubUk6yIN9t8yab2vyPtS8KV7OD/xQobcx7gztvR5h3 o1ToCXcM7FpW0wwNdXBMNn8BIz4y/0MjzItW1GeVfWj8u6d4U5R3EwVp5FfAqzj4MsML Mwif70QKTv9qRcPIX/ZNmSWLHvebHz+Cw9zyc0126ioUJyyaoZrMp44wavXfwC0InLDL 3jIw==
X-Gm-Message-State: AOJu0Yy1p9fLxFUIBhykb2xmiYIZ9GJZ9LiicLbSYIWBMk+sdc5EOL0W HPdR2r95zZdgUeqCIrmAcv+zOLgbcj637ZULu0nMVaACJIbKURHeKtgkrG6uEzkJGCXyMI1MzPs PXPe7On4b66ZHC8lG+MoJFpgW5sQ=
X-Google-Smtp-Source: AGHT+IHlYQofShFZLqWuhznRAqykojqMmz1qgIF4CY9QBStVRKFizQTzXXSnjz8u0UvFb1jjzohQKaAoBGPgxwUJtoM=
X-Received: by 2002:adf:f701:0:b0:337:4221:4d24 with SMTP id r1-20020adff701000000b0033742214d24mr2727232wrp.2.1706480358811; Sun, 28 Jan 2024 14:19:18 -0800 (PST)
MIME-Version: 1.0
References: <> <> <> <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
From: Abdussalam Baryun <>
Date: Mon, 29 Jan 2024 00:16:49 +0200
Message-ID: <>
To: Juliusz Chroboczek <>
Cc: Donald Eastlake <>, "" <>
Content-Type: multipart/alternative; boundary="0000000000009a6b91061008eb86"
Archived-At: <>
Subject: Re: [manet] AODVv2 implementation
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Mobile Ad-hoc Networks <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 28 Jan 2024 22:19:21 -0000

Hi Juliusz,

AODVv2 is still individual work and not adopted by this IETF WG.

On Sun, Jan 28, 2024 at 2:31 PM Juliusz Chroboczek <> wrote:

> Hi Donald,
> > I think that further exploration of AODVv2 and any AODV implementation
> problems
> > would be useful topics for the MNET WG and that we should consider
> adding that
> > to the Charter.
> I think that the people who know how to implement AODVv2 should give a talk
> on the subject (and perhaps write an informational I-D, if they are so
> inclined).

Until now no one made an input in this IETF WG that they will implement
AODVv2, if there is please refer me to such input. Also if there is then
they should make an informational or should co-author adopted reactive
routing standard for this WG.

> I, for one, would be interested in attending a technical talk
> on AODVv2 implementation, especially if some time is reserved for
> discussion.

I also interested but more interested in re-adopting AODVv2 and not
stoping it to be started again. Please note that this WG is not in a good
shape overall, please check the WG meeting and I will remind this WG
participants and this WG chairs that this IETF WG had got twice input from
our IETF AD responsible for MANET WG, which the AD informed the WG in two
different meeting that there is low discussion on the list and in meeting
and that this WG may conclude or that we need to recharter with willings of
adding work/efforts.

Therefore, because of low discussion/work and AD inputs, we need to adopt
work in WG which is important for this WG, especial our previous
adopeted_AODVv2 which was deleted and authors now are requesting
re-adoption. The input of the few participants which you were one of them
had reasonable concerns but if we see the full picture of this WG
re-charter situation and adding IETF AD input, I will say it is not needed
to stop adopting for this WG just because those concerns that don't have
details errors know about AODV or any experimental RFC for this WG.

> The chairs will correct me if I'm wrong, but I don't think that giving
> a talk during an IETF meeting requires rechartering.

I think any one participating to this WG can/could_have make a talk in this
WG even if we had 10 talks per meeting, but as I mentioned our situation in
this WG is having huge concerns/input from this WG AD and we need more
adopted_work/willing_to_author and more discussions related to
drafts/efforts/RFCs. Due to last meetings we had  few talks in our meeting
so if there is some one willing to talk about implementation they just
have/had to send a request on the list which was not seen sor far.

IMHO, the request for rechartering (which had not consensus results for
more than 4 months) was also because we had before request some drafts
requested for adoption and had low response of interest for adopting (
which I was interested and I responded maybe alone), and including AODVv2
had low response.

Overall, I think it was not reasonable that few participants may objected
adoption of well known AODV just because no seen implementation in open
source, especially within this time our WG AD is having serious concerns
regarding this WG to close it down or re-acharter shortly. I hope the WG
chair say something (or make an input on this list) regarding those AD
input and what is the situation exactly now for this WG?

Best Regards,