From nobody Mon May 1 06:01:28 2023 Return-Path: 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 B8FBCC159495 for ; Mon, 1 May 2023 06:01:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id My_vPkgqxmmc for ; Mon, 1 May 2023 06:01:26 -0700 (PDT) Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) (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 0C474C14CF0D for ; Mon, 1 May 2023 06:01:03 -0700 (PDT) Received: by mail-pj1-x1036.google.com with SMTP id 98e67ed59e1d1-24dfaff8794so1095420a91.3 for ; Mon, 01 May 2023 06:01:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682946062; x=1685538062; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=tywLx0wcAC9ATof2rJsw7MjUW/+jqBu9tDsFYRQFC2Y=; b=JcmGxy1ePmFoM5JO9GrLwIImVgXaGpnb7W0nkxaQUArmLQraKbd0UQuIkd7sumj8Wl FFxP4Lr61zNrpKoERaqXZ5N9OwNriLH79q94JaLKCQLDQnJK4r4hkTpOv+lhMF2gjpcM kUswrkUpMJ/65dVnzvCl6c3Fo+Z84mFInwfJMV/Z7j0aNli8B9rl5ymsZj0DTHLkRMb7 00J7Cs7Uq95L7WEr71uNlniJMB9QpdC4jS2jBhzrkUgxsJqQ+r7nfDM7PO+FGU/KqbxY QcAU5VVVmrAleQ1WsUQvFrfQJU8OXYAu4Z3KP8RYTJI3sBSZj0dRAgPbBbScTyBeHxvd rE5Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682946062; x=1685538062; h=content-transfer-encoding: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=tywLx0wcAC9ATof2rJsw7MjUW/+jqBu9tDsFYRQFC2Y=; b=LZJkiTpgxUVR1XbcBtK+6ZtylTvKdyK7eKRRGfS7ehymPe8opI1qjxiHAOVLYYY9I8 8hR1Wa6tdB8XoD0Ty9lnYtKyippFmvaFHy40IYbF883fs+eDyI9eXK6AwLvkR4kkRd9c 0A6odoR05o8KxQBlrvKrSgHdhNkuYx4uYbJCy+aY4whiSKFiq3R74bcZpeyk4i6ChcW5 OiNJJapbYBc/RIpfHReKunOg2+bAuls1Ut7iWE6XQya++9h4P/3viVbDv41vECyvh3ZG UB/J1zXSxKzmimK7ZBUp4ScnMtap0GbR3UKH7hauxAEAGYD+fgHS4mphOUGj+7SAfBWi pQJA== X-Gm-Message-State: AC+VfDwHLw9ZYHiD6mf8tw7FxBvnmt38EXktvJNNyoSwGUH7i97+rWVc LLZ6gJzXnBOT3rNfVpbvnChr0kVhO36v2zXaImfaoO29 X-Google-Smtp-Source: ACHHUZ5UuAAGQ3DOhJ6afx31mEWf6AAV8B5ipMv9jF/icoPHbkm6SwCoUG4Eglkwt4XdracExrfF8veGHS41gFiRIPo= X-Received: by 2002:a17:90b:4c84:b0:24e:807:bd09 with SMTP id my4-20020a17090b4c8400b0024e0807bd09mr2189980pjb.1.1682946062182; Mon, 01 May 2023 06:01:02 -0700 (PDT) MIME-Version: 1.0 References: <20230428120229.2CD1A55D5E@rfcpa.amsl.com> <6A3011F2-D55B-40E3-9156-A5DCEF5A763F@gmail.com> <6F5AB9FE-5869-42AB-8311-8ED4BA83C8ED@gmail.com> <3712F167-8859-4D69-B67C-2FAB2404DAD4@gmail.com> In-Reply-To: <3712F167-8859-4D69-B67C-2FAB2404DAD4@gmail.com> From: Henning Rogge Date: Mon, 1 May 2023 15:00:37 +0200 Message-ID: To: Christopher Dearlove Cc: "manet@ietf.org IETF" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Archived-At: Subject: Re: [manet] [Technical Errata Reported] RFC7466 (7477) X-BeenThere: manet@ietf.org 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: Mon, 01 May 2023 13:01:26 -0000 On Mon, May 1, 2023 at 2:55=E2=80=AFPM Christopher Dearlove wrote: > > If you know that the kink is cut off you would use the link quality mecha= nism to stop that link being considered symmetric, and thus would stop repo= rting it in TC messages (among other changes). Using link quality as a bina= ry good/bad state is a perfectly reasonable approach. But a little bit harsh for a link that might just have missed one/two Hellos... it might be the only link between two parts of the network. > You can=E2=80=99t adjust the link metric value in TC messages, because (a= ) you don=E2=80=99t know what it should be, and (b) you will create inconsi= stencies that could lead to looping. Just stopping reporting (updating sequ= ence number) is the best you can do. And using link quality does that. I can adjust the content of the TC my local router is producing... at the moment I am experimenting with a mechanism that will (as soon as a link is overdue based on Hello-Interval) use a similar "penalty" to the outgoing link metric in the local database than the metric algorithm (slightly modified DAT at the moment) does on the incoming one based on the time interval... which means this penalty will be instantly gone a new PacketBB packet arrives from the neighbor. It works quite well if both ends of the link run the same metric algorithm. Henning