Re: [manet] New DLEP extension draft for WG

Henning Rogge <hrogge@gmail.com> Fri, 29 January 2021 06:24 UTC

Return-Path: <hrogge@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 22AC43A0CC1 for <manet@ietfa.amsl.com>; Thu, 28 Jan 2021 22:24:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pkz6gnlXNfvn for <manet@ietfa.amsl.com>; Thu, 28 Jan 2021 22:24:47 -0800 (PST)
Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73CB83A0CBE for <manet@ietf.org>; Thu, 28 Jan 2021 22:24:47 -0800 (PST)
Received: by mail-lf1-x130.google.com with SMTP id e2so7327678lfj.13 for <manet@ietf.org>; Thu, 28 Jan 2021 22:24:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ISp8+ATc2Eyez5sS3Epa1tLU12j+q4aEIXFOYzrdei4=; b=USLysT2Ow6TRaeHHWDJDWvWWt2kQvn2aZAm7cnIdMwqqBp6XHpnjWGHJWqJQujOipJ GWktzSPLyjAw0lUc2EyVGABfNd7X1rMBTBgnYfwV4gzv+l5z9BpXlw+dm4dqdNNJZHTR tSu4eGFYwYrMV/r/WM7d6YVqeNkYdrpFJNXa7uUxWtqPWLW5hRoniWt02gVaFgd4GBZa 2QnGIr/elweSK0VoFHsDGnUF5NreOW2A/4uS6yx7eSm+ibSwtttg/nAEsHMwhVsaJMDZ 7aQ7WxDxeH0yUkK9eWUiqrh6INeiFCg5HcY4tOOZbvdIE5ZKUIjf4oFWyaWznBTMkIA3 3G5Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ISp8+ATc2Eyez5sS3Epa1tLU12j+q4aEIXFOYzrdei4=; b=Q6+jQoc1j1nNBlfdroLHuf2VGDYW8hH7cuTjBzAlGcEboqqyNX++GL84VFU3Nx9/+q h/0+EHFzdJee+i5hPzZlF4axCJRvD50fvI01+s69xMGdVM6z/bXF81SYq4tcixIEpSZ9 mw9nZ1SJDGGJJWsTfqAshi6Fbci2AbK08LI9hdFmbwzskw+r8JVAcJvCPjJ9H1eorUCS aaqOxrun+z+RYymm1WbqYmFSCgNyPAMqxdnAwDVkMx1nxq9gmLHQNiKL8YvB3vbOqGwc M6AUDYf7+be3iImq47EpMZqo0oDh1AmftExlM7VBAV8MtZ69ZRpTWOcN6T8JMBUkFVft 4q2A==
X-Gm-Message-State: AOAM531hF1Hza0736Tsc4dYeKWdSfbFrdLeSs5pb9JAFTgpWVK/a1gLf Td0GzZGZyOYg3ZIPczrVPHfXY9IPlz0lpssxD44TijqUzgE=
X-Google-Smtp-Source: ABdhPJw7oAVP/Gbro/n2nVz5hItmWWJz+5/Gj5knDhrzpabu9YGFSkqqRox/Zjf3yCo2edygH91idvPkKZzlRZpAAlw=
X-Received: by 2002:a19:8805:: with SMTP id k5mr1325279lfd.567.1611901485387; Thu, 28 Jan 2021 22:24:45 -0800 (PST)
MIME-Version: 1.0
References: <1611754401862.43329@fkie.fraunhofer.de> <a5e950b6c4ae0e0efb11d75ee748737bb4a59a30.camel@tropicalstormsoftware.com> <CAGnRvuoR8=sVjmwok-3SGrujULiBVMiDkp7d=HE-F7wejFWegw@mail.gmail.com> <CAGnRvuoNG62ycPQPaGH0f1W_yhfS0H-rE_KfpMD3=dfqeHvAYA@mail.gmail.com> <1611860125.2483.28.camel@gmail.com>
In-Reply-To: <1611860125.2483.28.camel@gmail.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Fri, 29 Jan 2021 07:24:19 +0100
Message-ID: <CAGnRvuoCZELvPO3uMdTqKJZ+kbngcSHY+gzu9JwJ4wJNM1VYqA@mail.gmail.com>
To: MANET IETF <manet@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/ILpvssPrFE9o-Onxrq88YNilyRM>
Subject: Re: [manet] New DLEP extension draft for WG
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 29 Jan 2021 06:24:49 -0000

On Thu, Jan 28, 2021 at 7:55 PM Rex Buddenberg <buddenbergr@gmail.com> wrote:
>
> Henning,
>
> On first read, this appears very sensible. Raises one question in my
> mind: how closely do these listings parallel MIB variables? Is there
> profit in casting these values as MIB extensions which would allow a
> network management console several hops away to do its job?

(I am replying to the mailing list so that all people can see it)

Hi,

I don't see any parallels with MIBs... I am not even aware of any MIB
for radio configuration at the IETF.

During the last years I have talked and worked with a few Radio
vendors and when asking about how to get metric and runtime data the
topic SNMP never came up. If you are lucky you get a REST interface
(and can point them to IETF standards like RESTCONF/RFC8040), if you
are unlucky you get a proprietary protocol on a proprietary network
socket.

There is also the fact that modern radio systems don't use fixed
values of frequency and bandwidth. Wifi 6 access points (as an
example) can use frequency division multiplexing to talk to several
clients at once... LTE (and earlier cellphone networks) have been
using dynamic time slot and bandwidth allocation for ages. This means
that the values can be neighbor specific, they can change quite often
and there might be radio systems where the router can ask for a better
radio band or more bandwidth.

Henning Rogge