Re: [manet] What was the Chameleon disaster?

Abdussalam Baryun <abdussalambaryun@gmail.com> Tue, 17 October 2023 14: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 19C49C17EB7B for <manet@ietfa.amsl.com>; Tue, 17 Oct 2023 07:42:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1bpABFOOMnlf for <manet@ietfa.amsl.com>; Tue, 17 Oct 2023 07:42:41 -0700 (PDT)
Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) (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 ietfa.amsl.com (Postfix) with ESMTPS id C061BC131921 for <manet@ietf.org>; Tue, 17 Oct 2023 07:42:00 -0700 (PDT)
Received: by mail-lj1-x229.google.com with SMTP id 38308e7fff4ca-2c50fbc218bso48876711fa.3 for <manet@ietf.org>; Tue, 17 Oct 2023 07:42:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1697553718; x=1698158518; darn=ietf.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=4GYXBpcRF0WftbwzEAecZDp6IiGlzneXutMXlsYmMPY=; b=ba1ZoZI6FMsPKJ5OxqRMx12ZLFMgJF7Xt5Sbj7othb998c5V0wLx8Y6CKqynsBsH3W JvwzRO5wGilARSi/v7WvPTrMinD2IKTzGEbn2m9vC2/nWo8RNWp3+eUaiwutpks62vqP E/u2K7rPsOSPEqMGWssnle/0W5I27ON/X5p9VhuL35YdRm8oZqZXVnjyU+XYNtv1fGPH vwJiVvXAFzeZYyS/7XWV2OF/rOb1NHBpE6CrrBsY6MNKyV6ErsfUIZIzsMDVddQAKj0G OKjN9D9UJKhrRBJa3yYyy0C+rHIDWSCnrghxrgo6ZGNWJRzzeDcnuW5RhMOc65wPsyHQ 7veA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697553718; x=1698158518; h=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=4GYXBpcRF0WftbwzEAecZDp6IiGlzneXutMXlsYmMPY=; b=hEOErS6OE9Q4yKQD3c5c2LL6NFOzdW8PzTD5TEyl2EdY/6tZtnft/sJiWbh0HTdNXY p48zXYwbXwQfL75Mkwn7/MQPMcoDTrOTgVH9U6JbOQpQH0ZdSXioOP4I9K1CyojPRyDX W87kO52Yv/k7o1vMO3p1YcR9kgNWeFHjGPXkRmE9WVrXHl1Z7DtsHtwptEBg+d9uvny3 hhkiNNFiWVfPOe29tz+jPlUwfMIptz77vQ5sgJnP0ZlUDsImff01ZmVaTalIIwx4bTsa 9AADuX/J6aT9SgGEBmzzfFkczzGqgJ7phZBS2bc2wdMosPjLuj7h8alXfbzuMSJHSeWp mZTQ==
X-Gm-Message-State: AOJu0Yzm5PHx0wWrWK3edYdqFuLViFYhgGzJDXDTOng4sI4NsnEsPRau Zti8ecMDrz/SJUtMiPI1hOw5/kknDujWZF8Xu2RQPAeWguI=
X-Google-Smtp-Source: AGHT+IG1rPzI9c08VRpzRYYPV5inWwc24PeSV5khAhUMayoXTuMgn7lykCd8c0NMYFUT1VfbYz3SMm3IOHglRI7bi6A=
X-Received: by 2002:a2e:b558:0:b0:2c5:1ad0:e306 with SMTP id a24-20020a2eb558000000b002c51ad0e306mr1735614ljn.8.1697553717620; Tue, 17 Oct 2023 07:41:57 -0700 (PDT)
MIME-Version: 1.0
References: <PH1P110MB114850D53A9A1E2C447C40EBB0D2A@PH1P110MB1148.NAMP110.PROD.OUTLOOK.COM> <CAGnRvuppwBb1bVVTUN6pD4tLwNmfZBw1_HP-6H_9eLV1=rgFFw@mail.gmail.com>
In-Reply-To: <CAGnRvuppwBb1bVVTUN6pD4tLwNmfZBw1_HP-6H_9eLV1=rgFFw@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
Date: Tue, 17 Oct 2023 16:30:57 +0200
Message-ID: <CADnDZ8_NEMvK9ZGQ6q4Eaw=N4oPWLQf_7_xeMBL32U0uSQ7Htw@mail.gmail.com>
To: "manet@ietf.org" <manet@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005374200607ea8659"
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/SR257dVgCxFEL-TKM5SRvZnFuK0>
Subject: Re: [manet] What was the Chameleon disaster?
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.39
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 17 Oct 2023 14:42:46 -0000

Hi MANET WG,

It is Good that we can get UK researchers participating/presenting and they
tried to add to our efforts in our WG. I think we do need
presentations/comments in this WG so we can get more participation
especially from  Asia or Africa.

However, IMHO the real reason of not re-presenting is not only no interest
but also I think it is difficult to build work within this WG, and
hopefully WG ADs can make it easier in the future, as we had seen in past
our reactive routing AODVv2 [1] (have taken  about 10 years building in
this WG, which was important milestone, but deleted in July 2016) was
killed by this IETF WG, which I think was real disappointing for me in this
WG, which we should never forget after our long discussions and effort of
many years for manet reactive routing milestone (may make some
participants/authors not interested in this WG to present at). Then the
AODVv2 work has been presented to another IETF WG to be build with some
modifications, however, someone may comment that that reactive routing work
maybe found a better place to be built at [2].

Additionally, there are many work that can be done in this WG, but was not
and there is possibility that some IETF participants prefered to make new
WG and new charter to make their efforts easier to build, work and
progress. I think IETF WGs need to be more acknowledging work/presentation
to come in and not to make it easier to go away to other SDOs.

Finally, the hybrid routing noted in the thread's subject was proposed by
one UK university researchers for the purpose of disaster response use
cases. So I think that draft/presentation was a Good start for this WG to
think/discuss about a disaster_use_case of being solved by hybrid routing
or by only proactive as OLSRv2.

AB

[1] https://datatracker.ietf.org/doc/html/draft-ietf-manet-aodvv2-16
[2] https://datatracker.ietf.org/doc/html/draft-ietf-roll-aodv-rpl-18